CVE-2024-45614: Header normalization allows for client to clobber proxy set headers in Puma
Noroxi assessment
Priority: Monitor (action score 21/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.64% (FIRST EPSS); higher than 51.2% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: puma (Debian:11) 4.3.8-1+deb11u3; puma (Debian:12) 5.6.5-3+deb12u1; puma (Debian:13) 6.4.3-1.
Low priority for now. Upgrade to puma (Debian:11) 4.3.8-1+deb11u3; puma (Debian:12) 5.6.5-3+deb12u1; puma (Debian:13) 6.4.3-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Puma is a Ruby/Rack web server built for parallelism. In affected versions clients could clobber values set by intermediate proxies (such as X-Forwarded-For) by providing a underscore version of the same header (X-Forwarded_For). Any users relying on proxy set variables is affected. v6.4.3/v5.6.9 now discards any headers using underscores if the non-underscore version also exists. Effectively, allowing the proxy defined headers to always win. Users are advised to upgrade. Nginx has a underscores_in_headers configuration variable to discard these headers at the proxy level as a mitigation. Any users that are implicitly trusting the proxy defined headers for security should immediately cease doing so until upgraded to the fixed versions.
- Published
- Sep 19, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.6% · 51th percentile
- CWE
- CWE-639
Report tools
Action score
21
Low priority for now.
- CVSS
- 21 / 40 · 5.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.4
- CNA · GitHub_M
- 5.4
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| puma | puma | cpe:2.3:a:puma:puma |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
puma puma
- >= 6.0.0, < 6.4.3, < 5.6.9affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- puma pumabefore 5.6.9
- puma puma6.0.0 and later · before 6.4.3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:11 | puma | before 4.3.8-1+deb11u3 | 4.3.8-1+deb11u3 |
| Debian:12 | puma | before 5.6.5-3+deb12u1 | 5.6.5-3+deb12u1 |
| Debian:13 | puma | before 6.4.3-1 | 6.4.3-1 |
| openSUSE:Leap 15.5 | rubygem-puma | before 4.3.12-150000.3.15.1 | 4.3.12-150000.3.15.1 |
| openSUSE:Leap 15.6 | rubygem-puma | before 5.6.9-150600.18.3.1 | 5.6.9-150600.18.3.1 |
| openSUSE:Tumbleweed | rubygem-puma | before 6.4.3-1.5 | 6.4.3-1.5 |
| openSUSE:Tumbleweed | rubygem-puma | before 6.4.3-1.3 | 6.4.3-1.3 |
| openSUSE:Tumbleweed | rubygem-puma | before 6.4.3-1.1 | 6.4.3-1.1 |
| RubyGems | puma | from 6.0.0 · before 6.4.3 | 6.4.3 |
| RubyGems | puma | before 5.6.9 | 5.6.9 |
| SUSE:Linux Enterprise High Availability Extension 15 SP2 | rubygem-puma | before 4.3.12-150000.3.15.1 | 4.3.12-150000.3.15.1 |
| SUSE:Linux Enterprise High Availability Extension 15 SP3 | rubygem-puma | before 5.6.9-150000.3.18.1 | 5.6.9-150000.3.18.1 |
| SUSE:Linux Enterprise High Availability Extension 15 SP6 | rubygem-puma | before 5.6.9-150600.18.3.1 | 5.6.9-150600.18.3.1 |
Same product
puma: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-40175Inconsistent Interpretation of HTTP Requests in puma39Monitor
- CVE-2022-24790HTTP Request Smuggling in puma31Monitor
- CVE-2020-11077HTTP Smuggling via Transfer-Encoding Header in Puma31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2022-23634Feb 11, 2022 · Information Exposure when using Puma with Rails24Monitor
- ← EarlierCVE-2024-21647Jan 8, 2024 · HTTP Request/Response Smuggling in puma30Monitor
- Later →CVE-2026-47736Jul 14, 2026 · Puma PROXY Protocol v1 Parser Allows Remote Memory Exhaustion30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:puma | 5.6.5-3+deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:rubygem-puma | 4.3.12-150000.3.15.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| RubyGems:puma | 5.6.9 | Package registry (OSV) |
| RubyGems:puma | 6.4.3 | Package registry (OSV) |
| suse:rubygem-puma | 4.3.12-150000.3.15.1 · SUSE:Linux Enterprise High Availability Extension 15 SP2 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2024-09-28 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+8 d
- TodayNov 16, 2026+788 d
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-639 · Authorization Bypass Through User-Controlled KeyCVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
nvd-primary
Root cause
The endpoint fetches the record by the ID sent in the request, but never checks whether the record belongs to the requesting user.
The bug in code
The whole CWE-639 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const invoice = await Invoice.findById(req.params.id);
res.json(invoice);Fixed
const invoice = await Invoice.findOne({
id: req.params.id,
ownerId: req.user.id,
});
if (!invoice) return res.sendStatus(404);
res.json(invoice);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.