CVE-2023-29197GHSA-WXMH-65F7-JCVW
Improper header name validation in guzzlehttp/psr7
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.9.1, 2.4.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
guzzlehttp/psr7 is a PSR-7 HTTP message library implementation in PHP. Affected versions are subject to 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. This is a follow-up to CVE-2022-24775 where the fix was incomplete. The issue has been patched in versions 1.9.1 and 2.4.5. There are no known workarounds for this vulnerability. Users are advised to upgrade.
Timeline
- CVE published
- Record last updated
Affected versions
- guzzle psr7
fixed in 1.9.1; From 2.0.0 · fixed in 2.4.5
- guzzlehttp/psr7Packagist
fixed in 1.9.1
- guzzlehttp/psr7Packagist
From 2.0.0 · fixed in 2.4.5