GitHub Advisoryadvisory · Packagist

GHSA-mcx4-f5f5-4859 Prevent cache poisoning via a Response Content-Type header in Symfony

LOW Published 2020-03-30 Modified 2021-01-08 Official page ↗
Aliases
CVE-2020-5255
Ecosystem
Packagist
Packages
symfony/http-foundation, symfony/symfony
Severity
Low
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L
Weaknesses
CWE-435
Reviewed
2020-03-30

Affected packages

• Packagist symfony/http-foundation: >= 4.4.0, < 4.4.7 → fixed in 4.4.7 • Packagist symfony/http-foundation: >= 5.0.0, < 5.0.7 → fixed in 5.0.7 • Packagist symfony/symfony: >= 4.4.0, < 4.4.7 → fixed in 4.4.7 • Packagist symfony/symfony: >= 5.0.0, < 5.0.7 → fixed in 5.0.7

Description

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.

Related

Alias · CVE (1)

  • CVE-2020-5255 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… vulnerability

Weakness · CWE (1)

  • CWE-435 Improper Interaction Between Multiple Correctly-Behaving Entities weakness

References