VulnWatch by ve1ve2
medium 5.3 EPSS 0.50%

GHSA-pcmh-g36c-qc44 / CVE-2025-1734: Streams HTTP wrapper does not fail for headers with invalid name and no colon

Source:
PHP releases (GitHub php/php-src tags)
Published:
Fetched:
Updated:
Affects:
php php-src

https://github.com/php/php-src/security/advisories/GHSA-pcmh-g36c-qc44 ↗

repo-advisorysecurityrepo:php/php-srcstack

Streams HTTP wrapper does not fail for headers with invalid name and no colon The headers without colon are currently returned without in `$http_response_header`. It means that something like: ``` printf "HTTP/1.0 200 Ok\r\nContent-Type: text/html\r\nWrong-Header\r\nGood-Header: test\r\n\r\nbody\r\n" |nc -l 0.0.0.0 8000 ``` results in following `$http_response_header` ``` array(4) { [0]=> string(15) "HTTP/1.0 200 Ok" [1]=> string(23) "Content-Type: text/html" [2]=> string(12) "Wrong-Header" [3]=> string(17) "Good-Header: test" } ``` In addition headers that contain a space in header name (before the colon) will also not fail which is not allowed by RFC. ### Impact This can allow issues in the application when parsing the array - e.g. application could consider it as a valid header or as a continuation of the previous one (currently folding header are misbehaving so there could be some logic for that in the application that could result in a security issue). So some sort of request smuggling could be possible in this case ### Workarounds Users can add a special handling of `$http_response_header`. No notification is triggered for this sort of header so no extra handling there is needed. Patched: 8.1.32, 8.2.28, 8.3.19, 8.4.5

Linked vulnerabilities (2)

CVE-2025-1734 medium 5.3 EPSS 0.50% (p44) NVDCVE.orgGHSA
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

php8.2 - security update

Aliases: CVE-2025-1217, CVE-2025-1219, CVE-2025-1736, CVE-2025-1861, GHSA-pcmh-g36c-qc44

Streams HTTP wrapper does not fail for headers with invalid name and no colon

Aliases: CVE-2025-1734