Improper header name validation in guzzlehttp/psr7
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| guzzle | psr7 | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-3705-1 | php-guzzlehttp-psr7 security update |
EUVD |
EUVD-2023-1416 | 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. |
Github GHSA |
GHSA-wxmh-65f7-jcvw | Improper header name validation in guzzlehttp/psr7 |
Ubuntu USN |
USN-6670-1 | php-guzzlehttp-psr7 vulnerabilities |
Ubuntu USN |
USN-6671-1 | php-nyholm-psr7 vulnerability |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: 1.2% (1.216% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.