dbcve.org
FedoraOperating system · Fedoraproject

CVE-2023-29197

HIGH · 7.5 CVSS v3.1 Published 2023-04-17
Fix available
A fix is available. Upgrade to 1.9.1 / 2.4.5 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The guzzlehttp/psr7 PHP library has improper header parsing that allows attackers to inject newline characters into HTTP header names and values. While RFC 7230 specifies CRLF (\r\n) sequences to terminate headers, many servers also accept LF (\n) alone, enabling HTTP response splitting or header injection attacks. This is an incomplete fix from CVE-2022-24775.

MitigationUpgrade guzzlehttp/psr7 to version 1.9.1 or 2.4.5. There are no workarounds; all affected deployments must upgrade to receive the patch.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FedoraOperating system
Affected:= 37= 38
Psr 7Application
Affected:< 1.9.1>= 2.0.0, < 2.4.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate guzzlehttp/psr7 installation
    Search for the guzzlehttp/psr7 library in your project by checking the vendor/guzzlehttp/psr7 directory, composer.json requires section, or composer.lock file for the psr7 package entry
    Affected if The guzzlehttp/psr7 package is present in your dependencies
  2. Determine installed psr7 version from composer
    Run 'composer show guzzlehttp/psr7' to display the installed version, or read the version from the 'version' field in the psr7 section of your composer.lock file
    Affected if The version displayed cannot be determined or is missing from dependency files
  3. Compare version against affected ranges
    Check if the installed version falls into < 1.9.1 or >= 2.0.0 and < 2.4.5 by comparing the version number you found
    Affected if The version is below 1.9.1, or is 2.0.0 through 2.4.4 inclusive
  4. Check Fedora system package (if applicable)
    If running on Fedora 37 or 38, run 'rpm -q guzzlehttp-psr7' to query the installed package version from the system package manager
    Affected if The system package version is below what Fedora ships as the fixed version (check against the affected Fedora versions 37 and 38)

Your environment is affected if guzzlehttp/psr7 version is found to be below 1.9.1, or between 2.0.0 and 2.4.4 inclusive, regardless of whether the library is used in a vulnerable way.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.9.1 / 2.4.5 or later
Fixed in 1.9.12.4.5
Interim mitigation

Upgrade guzzlehttp/psr7 to version 1.9.1 or 2.4.5. There are no workarounds; all affected deployments must upgrade to receive the patch.

Recommended fix High confidence

guzzlehttp/psr7 version 1.9.1 or 2.4.5 depending on your major version branch

  1. Identify the current version of guzzlehttp/psr7 in your project by checking your composer.json or lock file
  2. If using version 1.x (< 1.9.1): Run 'composer require guzzlehttp/psr7:^1.9.1' to upgrade to the fixed version
  3. If using version 2.x (>= 2.0.0 and < 2.4.5): Run 'composer require guzzlehttp/psr7:^2.4.5' to upgrade to the fixed version
  4. Run 'composer update guzzlehttp/psr7' to apply the changes
  5. Verify the installed version matches the expected fixed version using 'composer show guzzlehttp/psr7'
  6. Test your application thoroughly to ensure the upgrade does not break existing functionality
Caveat No breaking changes reported for this security patch; minor version upgrades should be safe

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fedora Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-29197 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-29197 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data