MediumGHSA-wxmh-65f7-jcvwCVE-2023-29197
Improper header name validation in guzzlehttp/psr7
Published 19 Apr 2023 · Updated 4 Feb 2026
Affected packages
guzzlehttp/psr7Composer
- Affected
- <1.9.1
- Fixed in
- 1.9.1
Update to the fixed version for your release line, for example:
composer require guzzlehttp/psr7:^1.9.1guzzlehttp/psr7Composer
- Affected
- >=2.0.0 <2.4.5
- Fixed in
- 2.4.5
Update to the fixed version for your release line, for example:
composer require guzzlehttp/psr7:^2.4.5Details
Impact
Improper header parsing. An attacker could sneak in a newline (\n) into both the header names and values. While the specification states that \r\n\r\n is used to terminate the header list, many servers in the wild will also accept \n\n.
Patches
The issue is patched in 1.9.1 and 2.4.5.
Workarounds
There are no known workarounds.
References
- https://www.rfc-editor.org/rfc/rfc7230#section-3.2.4
Is GHSA-wxmh-65f7-jcvw in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected guzzlehttp/psr7, and gives you the command that fixes it.
References
- Linkgithub.com/guzzle/psr7/security/advisories/GHSA-q7rv-6hp3-vh96
- Linkgithub.com/guzzle/psr7/security/advisories/GHSA-wxmh-65f7-jcvw
- Advisorynvd.nist.gov/vuln/detail/CVE-2023-29197
- Linkcve.mitre.org/cgi-bin/cvename.cgi?name=2022-24775
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/guzzlehttp/psr7/CVE-2023-29197.yaml
- Packagegithub.com/guzzle/psr7
- Linklists.debian.org/debian-lts-announce/2023/12/msg00028.html
- Linklists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FJANWDXJZE5BGLN4MQ4FEHV5LJ6CMKQF
- Linklists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/O35UN4IK6VS2LXSRWUDFWY7NI73RKY2U
- Linkwww.rfc-editor.org/rfc/rfc7230#section-3.2.4
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.