GHSA-mcx4-f5f5-4859LowCVSS 2.6

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

Published
March 30, 2020
Last Modified
February 5, 2024

🔗 CVE IDs covered (1)

📋 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.

🎯 Affected products4

  • composer/symfony/http-foundation:>= 4.4.0, < 4.4.7
  • composer/symfony/http-foundation:>= 5.0.0, < 5.0.7
  • composer/symfony/symfony:>= 4.4.0, < 4.4.7
  • composer/symfony/symfony:>= 5.0.0, < 5.0.7

🔗 References (9)