{"vuln_id":"GHSA-pcmh-g36c-qc44","aliases":["CVE-2025-1734"],"description":"Streams HTTP wrapper does not fail for headers with invalid name and no colon","published_at":"2025-03-13T17:43:58Z","modified_at":"2025-03-13T17:43:58Z","first_seen_at":"2026-11-22T14:05:37.616634Z","severity":"medium","severity_source":"ghsa","cvss_score":null,"cvss_vector":null,"cwe":[],"vendor":null,"product":null,"kev":{"is_kev":false,"date_added":null,"due_date":null,"ransomware":false},"epss":null,"epss_percentile":null,"nvd_status":null,"enriched_at":null,"links":{"nvd":"https://github.com/advisories/GHSA-pcmh-g36c-qc44"},"matched_alias":null,"items":[{"id":12659,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-pcmh-g36c-qc44 / CVE-2025-1734: Streams HTTP wrapper does not fail for headers with invalid name and no colon","summary":"Streams HTTP wrapper does not fail for headers with invalid name and no colon\n\nThe headers without colon are currently returned without in `$http_response_header`. It means that something like:\r\n\r\n```\r\nprintf \"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\r\n```\r\n\r\nresults in following  `$http_response_header`\r\n\r\n```\r\narray(4) {\r\n  [0]=>\r\n  string(15) \"HTTP/1.0 200 Ok\"\r\n  [1]=>\r\n  string(23) \"Content-Type: text/html\"\r\n  [2]=>\r\n  string(12) \"Wrong-Header\"\r\n  [3]=>\r\n  string(17) \"Good-Header: test\"\r\n}\r\n```\r\n\r\nIn addition headers that contain a space in header name (before the colon) will also not fail which is not allowed by RFC.\r\n\r\n### Impact\r\n\r\nThis 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\r\n\r\n### Workarounds\r\n\r\nUsers 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.\r\n\nPatched:  8.1.32,  8.2.28,  8.3.19,  8.4.5","url":"https://github.com/php/php-src/security/advisories/GHSA-pcmh-g36c-qc44","published_at":"2025-03-13T17:43:58Z","updated_at":"2025-03-13T17:43:58Z","fetched_at":"2026-11-22T14:05:37.431192Z","severity":"medium","cvss_score":5.3,"epss":0.00502,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"php-src","vuln_id":"CVE-2025-1734","vuln_ids":["CVE-2025-1217","CVE-2025-1219","CVE-2025-1734","CVE-2025-1736","CVE-2025-1861","GHSA-PCMH-G36C-QC44"],"tags":["repo-advisory","security","repo:php/php-src","stack"],"cluster_id":11767,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12659","html":"https://vulnwatch.ve1ve2.com/item/12659"}}]}