CVE-2020-5255: Prevent cache poisoning via a Response Content-Type header

Published Mar 30, 2020
·
Updated

CVE-2020-5255: Prevent cache poisoning via a Response Content-Type header

Other sources

Description -----------

When a Response does not contain a Content-Type header, Symfony falls back 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 lead to a corrupted cache where the cached format is not the right one.

Resolution ----------

Symfony does not use the Accept header anymore to guess the Content-Type.

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

Credits -------

I would like to thank Xavier Lacot from JoliCode for reporting & Yonel Ceruto and Tobias Schultze for fixing the issue.

GitHub

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.

Affected Software

8 affected componentsFixes available
composer/symfony/http-foundation>=4.4.0, <4.4.7, >=5.0.0, <5.0.7
composer/symfony/symfony>=4.4.0, <4.4.7, >=5.0.0, <5.0.7
composer/symfony/symfony>=5.0.0<5.0.7
5.0.7
composer/symfony/symfony>=4.4.0<4.4.7
4.4.7
composer/symfony/http-foundation>=5.0.0<5.0.7
5.0.7
composer/symfony/http-foundation>=4.4.0<4.4.7
4.4.7
SensioLabs Symfony>=4.4.0<4.4.7
SensioLabs Symfony>=5.0.0<5.0.7

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 5.0.7
  2. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 4.4.7
  3. Upgrade

    Upgrade composer/symfony/http-foundation to a version that resolves this vulnerability.

    Fixed in 5.0.7
  4. Upgrade

    Upgrade composer/symfony/http-foundation to a version that resolves this vulnerability.

    Fixed in 4.4.7
  5. Upgrade

    Upgrade Symfony to a version that resolves this vulnerability.

    Fixed in 4.4.7
  6. Upgrade

    Upgrade Symfony to a version that resolves this vulnerability.

    Fixed in 5.0.7

Event History

Mar 30, 2020
Advisory Published
02:00 PM
CVE Published
via MITRE·07:30 PM
Data Sourced
via MITRE·07:30 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:15 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is CVE-2020-5255?

CVE-2020-5255 is a vulnerability that allows cache poisoning via a Response Content-Type header.

2

What is the severity of CVE-2020-5255?

The severity of CVE-2020-5255 is medium with a CVSS score of 4.3.

3

How does CVE-2020-5255 affect Symfony?

Versions of Symfony before 4.4.7 and 5.0.7 are affected by CVE-2020-5255.

4

How can I fix CVE-2020-5255?

To fix CVE-2020-5255, upgrade to Symfony version 4.4.7 or 5.0.7 or later.

5

Where can I find more information about CVE-2020-5255?

You can find more information about CVE-2020-5255 at the following references: [link1] [link2] [link3].

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203