CVE-2022-24775 json
Improper Input Validation in guzzlehttp/psr7
published 4y ago modified last mo. also BIT-drupal-2022-24775 , DRUPAL-CORE-2022-006 , EUVD-2022-1513 , GHSA-q7rv-6hp3-vh96
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.5%
- EPSS 2.5% chance of exploitation in 30 days, percentile 84%
- public exploits
- 0
- none known
Summary
guzzlehttp/psr7 is a PSR-7 HTTP message library. Versions prior to 1.8.4 and 2.1.1 are vulnerable to improper header parsing. An attacker could sneak in a new line character and pass untrusted values. The issue is patched in 1.8.4 and 2.1.1. There are currently no known workarounds.
Patch / fix
- packagist guzzlehttp/psr7 1.8.4, 2.1.1
- bitnami drupal 9.2.16, 9.3.9
- packagist drupal/core 9.2.16, 9.3.9
- drupal drupal 9.2.16, 9.3.9
- guzzlephp psr-7 1.8.4, 2.1.1
- php-guzzlehttp-psr7 Debian 14, Debian 13, Debian 12 1.8.5-1
debian advisories DEBIAN-CVE-2022-24775
- php-guzzlehttp-psr7 Ubuntu 20.04 LTS 1.4.2-0.1+deb10u2build0.20.04.1
- php-guzzlehttp-psr7 Ubuntu Pro 22.04 LTS 1.8.3-1ubuntu0.1~esm1
ubuntu advisories UBUNTU-CVE-2022-24775
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- github.com/guzzle/psr7#485 commit
- github.com/guzzle/psr7#486 commit
- drupal.org/sa-core-2022-006 advisory
Is CVE-2022-24775 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-24775 updated cvss 7.5
php-guzzlehttp-psr7: improper header parsing in php-guzzlehttp-psr7
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
2.48% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
| OSV | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | guzzlehttp/psr7 | <1.8.4 >=2.0.0, <2.1.1 |
1.8.4 2.1.1 |
| bitnami | drupal | >=8.0.0, <9.2.16 >=9.3.0, <9.3.9 |
9.2.16 9.3.9 |
| packagist | drupal/core | >=8.0.0, <9.2.16 >=9.3.0, <9.3.9 |
9.2.16 9.3.9 |
Affected products
- guzzle psr7
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
github.com
/guzzle/psr7/pull/485/commits/e55afaa3fc138c89adf3b55a8ba20dc60d17f1f1
web, patch, third-party-advisory, advisory
-
github.com
/guzzle/psr7/pull/486/commits/9a96d9db668b485361ed9de7b5bf1e54895df1dc
web, patch, third-party-advisory, advisory
-
drupal.org
/sa-core-2022-006
web, patch, third-party-advisory, advisory
-
github.com
/guzzle/psr7/security/advisories/GHSA-q7rv-6hp3-vh96
web, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-24775
advisory, web
-
github.com
/FriendsOfPHP/security-advisories/blob/master/guzzlehttp/psr7/CVE-2022-24775.yaml
web
-
github.com
/guzzle/psr7
package
-
rfc-editor.org
/rfc/rfc7230#section-3.2.4
web
Sources
- CVE List CVE-2022-24775
- GitHub Advisory GHSA-q7rv-6hp3-vh96
- NVD CVE-2022-24775
- OSV BIT-drupal-2022-24775
- OSV DRUPAL-CORE-2022-006
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.