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

CVE-2020-5255 · Severity: low · CVSS 3.1 · Published 2020-03-30

Prevent cache poisoning via a Response Content-Type header in Symfony

Technologies: symfony/http-foundation (Packagist), symfony/symfony (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2020-5255 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2020-5255 being exploited in the wild.
How severe is CVE-2020-5255?
Low severity, with a CVSS score of 3.1, published 30 March 2020.
Which products and versions are affected?
symfony/http-foundation (Packagist) ECOSYSTEM:introduced=4.4.0,fixed=4.4.7; symfony/symfony (Packagist) ECOSYSTEM:introduced=4.4.0,fixed=4.4.7.
Is there a fix for CVE-2020-5255?
Yes. symfony/http-foundation (Packagist): upgrade to 4.4.7 or later; symfony/symfony (Packagist): upgrade to 4.4.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2020-5255?
Check whether you run symfony/http-foundation (Packagist) or symfony/symfony (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • symfony/http-foundation (Packagist): upgrade to 4.4.7 or later
    composer require symfony/http-foundation:^4.4.7
  • symfony/symfony (Packagist): upgrade to 4.4.7 or later
    composer require symfony/symfony:^4.4.7

Affected products

  • symfony/http-foundation (Packagist) ECOSYSTEM:introduced=4.4.0,fixed=4.4.7
  • symfony/symfony (Packagist) ECOSYSTEM:introduced=4.4.0,fixed=4.4.7

Identifiers

  • CVE-2020-5255
  • GHSA-mcx4-f5f5-4859

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.