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

TRUNG BÌNH 4.3CVE-2020-5255 · BIT-symfony-2020-5255 · GHSA-mcx4-f5f5-4859 · Công bố 30/03/2020 · cập nhật 17/06/2026

Tóm tắt nhanh

CVE-2020-5255 là lỗ hổng mức TRUNG BÌNH (CVSS 4.3) ảnh hưởng symfony/http-foundation, symfony/symfony, symfony (sensiolabs).
Xác suất bị khai thác trong 30 ngày tới (EPSS): 1.3%, cao hơn 70.4% các lỗ hổng khác.
Cách xử lý: cập nhật lên 4.4.7, 5.0.7 hoặc mới hơn.

Gói / sản phẩm	Phiên bản bị ảnh hưởng	Phiên bản đã vá
symfony/http-foundation Packagist	`≥ 4.4.0, < 4.4.7≥ 5.0.0, < 5.0.7`	`4.4.75.0.7`
symfony/symfony Packagist	`≥ 4.4.0, < 4.4.7≥ 5.0.0, < 5.0.7`	`4.4.75.0.7`
symfony sensiolabs	`≥ 4.4.0, < 4.4.7≥ 5.0.0, < 5.0.7`	`4.4.75.0.7`

Mô tả

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.

Mô tả của NVD

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.