CVE-2020-5255GHSA-MCX4-F5F5-4859BIT-SYMFONY-2020-5255
Prevent cache poisoning via a Response Content-Type header
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.4.7, 5.0.7
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In Symfony before versions 4.4.7 and 5.0.7, when a `Response` does not contain a `Content-Type` header, affected versions of Symfony can fallback to the format defined in the `Accept` header of the request, leading to a possible mismatch between the response's content and `Content-Type` header. When the response is cached, this can prevent the use of the website by other users. This has been patched in versions 4.4.7 and 5.0.7.
Timeline
- CVE published
- Record last updated
Affected versions
- symfony symfony
Version range not reported
- symfony/http-foundationPackagist
From 4.4.0 · fixed in 4.4.7
- symfony/http-foundationPackagist
From 5.0.0 · fixed in 5.0.7
- symfony/symfonyPackagist
From 4.4.0 · fixed in 4.4.7
- symfony/symfonyPackagist
From 5.0.0 · fixed in 5.0.7