What is CVE-2022-24894?

CVE-2022-24894 is a medium-severity security vulnerability in symfony/http-kernel (composer), affecting versions >= 2.0.0, < 4.4.50. It is fixed in 4.4.50, 5.4.20, 6.0.20, 6.1.12, 6.2.6.

How severe is CVE-2022-24894?

CVE-2022-24894 has a CVSS score of 5.9 (Medium). 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-24894?

symfony/http-kernel (composer) versions >= 2.0.0, = 2.0.0, < 4.4.50.

Is there a fix for CVE-2022-24894?

Yes. CVE-2022-24894 is fixed in 4.4.50, 5.4.20, 6.0.20, 6.1.12, 6.2.6. Upgrade to this version or later.

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

Whether CVE-2022-24894 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-24894 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.

CVE-2022-24894 in symfony/http-kernel

Q: How severe is CVE-2022-24894?

CVE-2022-24894 has a CVSS score of 5.9 (Medium). 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-24894?

symfony/http-kernel (composer) versions >= 2.0.0, = 2.0.0, < 4.4.50.

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

Yes. CVE-2022-24894 is fixed in 4.4.50, 5.4.20, 6.0.20, 6.1.12, 6.2.6. Upgrade to this version or later.

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

Whether CVE-2022-24894 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-24894 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-24894?

Upgrade: symfony/http-kernel to 4.4.50 or later, symfony/http-kernel to 5.4.20 or later, symfony/http-kernel to 6.0.20 or later, symfony/http-kernel to 6.1.12 or later, symfony/http-kernel to 6.2.6 or later, symfony/symfony to 4.4.50 or later, symfony/symfony to 5.4.20 or later, symfony/symfony to 6.0.20 or later, symfony/symfony to 6.1.12 or later, symfony/symfony to 6.2.6 or later.

Summary

Symfony storing cookie headers in HttpCache

Description

The Symfony HTTP cache system acts as a reverse proxy: it caches HTTP responses (including headers) and returns them to clients.

In a recent AbstractSessionListener change, the response might now contain a Set-Cookie header. If the Symfony HTTP cache system is enabled, this header might be stored and returned to some other clients. An attacker can use this vulnerability to retrieve the victim's session.

Resolution

The HttpStore constructor now takes a parameter containing a list of private headers that are removed from the HTTP response headers.
The default value for this parameter is Set-Cookie, but it can be overridden or extended by the application.

The patch for this issue is available here for branch 4.4.

Credits

We would like to thank Soner Sayakci for reporting the issue and Nicolas Grekas for fixing it.

Impact

CVE-2022-24894 has a CVSS score of 5.9 (Medium). The vector is network-reachable, low privileges required, and user interaction required. 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.4.50, 5.4.20, 6.0.20, 6.1.12, 6.2.6); upgrading removes the vulnerable code path.

Affected versions

symfony/http-kernel (>= 2.0.0, < 4.4.50) symfony/http-kernel (>= 5.0.0, < 5.4.20) symfony/http-kernel (>= 6.0.0, < 6.0.20) symfony/http-kernel (>= 6.1.0, < 6.1.12) symfony/http-kernel (>= 6.2.0, < 6.2.6) symfony/symfony (>= 2.0.0, < 4.4.50) symfony/symfony (>= 5.0.0, < 5.4.20) symfony/symfony (>= 6.0.0, < 6.0.20) symfony/symfony (>= 6.1.0, < 6.1.12) symfony/symfony (>= 6.2.0, < 6.2.6)

Security releases

symfony/http-kernel → 4.4.50 (composer) symfony/http-kernel → 5.4.20 (composer) symfony/http-kernel → 6.0.20 (composer) symfony/http-kernel → 6.1.12 (composer) symfony/http-kernel → 6.2.6 (composer) symfony/symfony → 4.4.50 (composer) symfony/symfony → 5.4.20 (composer) symfony/symfony → 6.0.20 (composer) symfony/symfony → 6.1.12 (composer) symfony/symfony → 6.2.6 (composer)

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

Upgrade the following packages to resolve this vulnerability:

symfony/http-kernel to 4.4.50 or later; symfony/http-kernel to 5.4.20 or later; symfony/http-kernel to 6.0.20 or later; symfony/http-kernel to 6.1.12 or later; symfony/http-kernel to 6.2.6 or later; symfony/symfony to 4.4.50 or later; symfony/symfony to 5.4.20 or later; symfony/symfony to 6.0.20 or later; symfony/symfony to 6.1.12 or later; symfony/symfony to 6.2.6 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2022-24894? CVE-2022-24894 is a medium-severity security vulnerability in symfony/http-kernel (composer), affecting versions >= 2.0.0, < 4.4.50. It is fixed in 4.4.50, 5.4.20, 6.0.20, 6.1.12, 6.2.6.
How severe is CVE-2022-24894? CVE-2022-24894 has a CVSS score of 5.9 (Medium). 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-24894?
- symfony/http-kernel (composer) (versions >= 2.0.0, < 4.4.50)
- symfony/symfony (composer) (versions >= 2.0.0, < 4.4.50)
Is there a fix for CVE-2022-24894? Yes. CVE-2022-24894 is fixed in 4.4.50, 5.4.20, 6.0.20, 6.1.12, 6.2.6. Upgrade to this version or later.
Is CVE-2022-24894 exploitable, and should I be worried? Whether CVE-2022-24894 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-24894 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-24894?
- Upgrade symfony/http-kernel to 4.4.50 or later
- Upgrade symfony/http-kernel to 5.4.20 or later
- Upgrade symfony/http-kernel to 6.0.20 or later
- Upgrade symfony/http-kernel to 6.1.12 or later
- Upgrade symfony/http-kernel to 6.2.6 or later
- Upgrade symfony/symfony to 4.4.50 or later
- Upgrade symfony/symfony to 5.4.20 or later
- Upgrade symfony/symfony to 6.0.20 or later
- Upgrade symfony/symfony to 6.1.12 or later
- Upgrade symfony/symfony to 6.2.6 or later

Other vulnerabilities in symfony/http-kernel

CVE-IDSeverityPackage summary

CVE-2026-45075Highsymfony/http-kernel: Symfony's HEAD Request Bypasses methods: ['GET'] Filter in #[IsGranted] / #[IsSignatureValid] / #[IsCsrfTokenValid]CVE-2014-5245Highsymfony/http-kernel: Symfony allows direct access of ESI URLs behind a trusted proxy CVE-2015-2308Mediumsymfony/symfony: Symfony Vulnerable to PHP Eval Injection CVE-2015-4050Mediumsymfony/http-kernel: Symfony Incorrect Access Control CVE-2019-18887Highsymfony/http-kernel: Symfony Http-Kernel has non-constant time comparison in UriSigner