What is CVE-2022-24822?

CVE-2022-24822 is a high-severity security vulnerability in @podium/layout (npm), affecting versions < 4.6.110. It is fixed in 4.6.110, 4.2.74.

How severe is CVE-2022-24822?

CVE-2022-24822 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which packages are affected by CVE-2022-24822?

@podium/layout (npm) versions < 4.6.110; @podium/proxy (npm) versions < 4.2.74.

Is there a fix for CVE-2022-24822?

Yes. CVE-2022-24822 is fixed in 4.6.110, 4.2.74. Upgrade to this version or later.

Is CVE-2022-24822 exploitable, and should I be worried?

Whether CVE-2022-24822 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2022-24822 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2022-24822?

Upgrade: @podium/layout to 4.6.110 or later, @podium/proxy to 4.2.74 or later.

CVE-2022-24822 in @podium/layout

Q: How severe is CVE-2022-24822?

CVE-2022-24822 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which packages are affected by CVE-2022-24822?

@podium/layout (npm) versions < 4.6.110; @podium/proxy (npm) versions < 4.2.74.

Q: Is there a fix for CVE-2022-24822?

Yes. CVE-2022-24822 is fixed in 4.6.110, 4.2.74. Upgrade to this version or later.

Q: Is CVE-2022-24822 exploitable, and should I be worried?

Whether CVE-2022-24822 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2022-24822 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2022-24822?

Upgrade: @podium/layout to 4.6.110 or later, @podium/proxy to 4.2.74 or later.

Summary

Denial of Service vulnerability in @podium/layout and @podium/proxy

Workarounds

It is not easily possible to work around this issue without upgrading. We recommend upgrading @podium/layout and/or @podium/proxy as soon as possible.

For more information

If you have any questions or comments about this advisory:

Open an issue in podium-lib/issues

Credits

The vulnerability was reported by krynos from Ercoli Consulting via FINN.no's private bug bounty program

Impact

An attacker using the Trailer header as part of the request against proxy endpoints has the ability to take down the server.
All Podium layouts that include podlets with proxy endpoints are affected.

CVE-2022-24822 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.6.110, 4.2.74); upgrading removes the vulnerable code path.

Affected versions

@podium/layout (< 4.6.110) @podium/proxy (< 4.2.74)

Security releases

@podium/layout → 4.6.110 (npm) @podium/proxy → 4.2.74 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

@podium/layout which is the main way developers/users are vulnerable to this exploit, has been patched in version 4.6.110. All earlier versions are vulnerable.
@podium/proxy which is the source of the vulnerability and is used by @podium/layout has been patched in version 4.2.74. All earlier versions are vulnerable.

Frequently Asked Questions

What is CVE-2022-24822? CVE-2022-24822 is a high-severity security vulnerability in @podium/layout (npm), affecting versions < 4.6.110. It is fixed in 4.6.110, 4.2.74.
How severe is CVE-2022-24822? CVE-2022-24822 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which packages are affected by CVE-2022-24822?
- @podium/layout (npm) (versions < 4.6.110)
- @podium/proxy (npm) (versions < 4.2.74)
Is there a fix for CVE-2022-24822? Yes. CVE-2022-24822 is fixed in 4.6.110, 4.2.74. Upgrade to this version or later.
Is CVE-2022-24822 exploitable, and should I be worried? Whether CVE-2022-24822 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2022-24822 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2022-24822?
- Upgrade @podium/layout to 4.6.110 or later
- Upgrade @podium/proxy to 4.2.74 or later