FedoraOperating system · Fedoraproject
CVE-2023-29530
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 · uneditedLaminas Diactoros provides PSR HTTP Message implementations. In versions 2.18.0 and prior, 2.19.0, 2.20.0, 2.21.0, 2.22.0, 2.23.0, 2.24.0, and 2.25.0, users who create HTTP requests or responses using laminas/laminas-diactoros, when providing a newline at the start or end of a header key or value, can cause an invalid message. This can lead to denial of service vectors or application errors. The problem has been patched in following versions 2.18.1, 2.19.1, 2.20.1, 2.21.1, 2.22.1, 2.23.1, 2.24.1, and 2.25.1. As a workaround, validate HTTP header keys and/or values, and if using user-supplied values, filter them to strip off leading or trailing newline characters before calling `withHeader()`.
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 confidenceLaminas Diactoros (a PSR HTTP Message implementation for PHP) fails to sanitize leading/trailing newline characters in HTTP header keys and values. When requests or responses are created with newlines in headers, it creates invalid HTTP messages that can cause denial of service or application errors.
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
= 38< 2.18.1= 2.19.0= 2.20.0= 2.21.0= 2.22.0= 2.23.0= 2.24.0= 2.25.0< 1.9.1>= 2.0.0, < 2.4.5CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Check Laminas Diactoros versionRun `composer show laminas/laminas-diactoros` or inspect the version in your composer.lock fileAffected if The installed version is less than 2.18.1, or equals 2.19.0, 2.20.0, 2.21.0, 2.22.0, 2.23.0, 2.24.0, or 2.25.0
-
Check Guzzle PSR7 versionRun `composer show guzzlehttp/psr7` or inspect the version in your composer.lock fileAffected if The installed version is less than 1.9.1, or is 2.0.0 through 2.4.4
-
Identify if the application processes user-supplied header valuesSearch your codebase for calls to withHeader(), setHeader(), or similar header-setting methods that accept user input (e.g., from $_GET, $_POST, $_SERVER, request body parameters, or HTTP request headers)Affected if User-controlled input flows into header-setting methods without prior validation to strip leading/trailing newlines
-
Check Fedora version if running on FedoraRun `cat /etc/fedora-release` or `rpm -q fedora-release`Affected if Running Fedora 38 (which ships the vulnerable Laminas Diactoros package)
You are affected if you have Laminas Diactoros or Guzzle PSR7 in your dependencies at a vulnerable version AND your application passes unsanitized user input into HTTP header methods.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.9.12.4.52.18.1
Upgrade laminas/laminas-diactoros to version 2.18.1, 2.19.1, 2.20.1, 2.21.1, 2.22.1, 2.23.1, 2.24.1, or 2.25.1. Alternatively, validate and strip leading/trailing newlines from header values before calling withHeader().
Upgrade to 2.25.1 (latest) or the appropriate patched version for your branch: 2.18.1, 2.19.1, 2.20.1, 2.21.1, 2.22.1, 2.23.1, 2.24.1, or 2.25.1
- Identify the currently installed version of laminas/laminas-diactoros (e.g., run `composer show laminas/laminas-diactoros` or check your composer.lock)
- Determine which version branch you are on (2.18.x, 2.19.x, 2.20.x, 2.21.x, 2.22.x, 2.23.x, 2.24.x, or 2.25.x)
- Run `composer require laminas/laminas-diactoros:^2.18.1` (or appropriate version for your branch) to update to the patched release
- Alternatively, for Fedora systems, run `sudo dnf update laminas-diactoros` to install the patched version
- Verify the new version is installed: `composer show laminas/laminas-diactoros`
- Test your application to confirm HTTP headers with leading/trailing newlines are now properly rejected with an exception
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fedora
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-29530 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-29530 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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