Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2022-24790: HTTP Request Smuggling in puma

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 2.1% (FIRST EPSS); higher than 82.5% 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. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: puma puma 5.6.4.

Low priority for now. Upgrade to puma puma 5.6.4 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 simple, fast, multi-threaded, parallel HTTP 1.1 server for Ruby/Rack applications. When using Puma behind a proxy that does not properly validate that the incoming HTTP request matches the RFC7230 standard, Puma and the frontend proxy may disagree on where a request starts and ends. This would allow requests to be smuggled via the front-end proxy to Puma. The vulnerability has been fixed in 5.6.4 and 4.3.12. Users are advised to upgrade as soon as possible. Workaround: when deploying a proxy in front of Puma, turning on any and all functionality to make sure that the request matches the RFC7230 standard.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
Mar 30, 2022
Updated
Jun 17, 2026
EPSS
2.1% · 82th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.1%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.5
CNA · GitHub_M
9.1
1.6 point gap

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

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
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-24790

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for puma records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi 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 help

Affected 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.

VendorProduct
pumapuma
debiandebian linux
fedoraprojectfedora

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux10.0
  • debian debian linux11.0
  • fedoraproject fedora35
  • fedoraproject fedora36
  • fedoraproject fedora37
  • puma puma5.0.0 and later · before 5.6.4
  • puma pumabefore 4.3.12

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

    • < 4.3.12, >= 5.0.0, < 5.6.4affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:10pumabefore 3.12.0-2+deb10u33.12.0-2+deb10u3
Debian:11pumabefore 4.3.8-1+deb11u24.3.8-1+deb11u2
Debian:12pumabefore 5.6.4-15.6.4-1
openSUSE:Leap 15.3rubygem-pumabefore 4.3.12-150000.3.9.14.3.12-150000.3.9.1
openSUSE:Tumbleweedruby3.2-rubygem-puma-5before 5.6.5-1.75.6.5-1.7
openSUSE:Tumbleweedrubygem-puma-4before 4.3.12-1.14.3.12-1.1
openSUSE:Tumbleweedrubygem-puma-5before 5.6.8-1.15.6.8-1.1
openSUSE:Tumbleweedrubygem-puma-5before 5.6.5-1.15.6.5-1.1
Red Hat:satellite:6.9::el7tfm-rubygem-pumabefore 0:4.3.12-1.el7sat0:4.3.12-1.el7sat
Red Hat:satellite:6.9::el7tfm-rubygem-puma-debuginfobefore 0:4.3.12-1.el7sat0:4.3.12-1.el7sat
Red Hat:storage:3.5:wa:el7grafanabefore 0:5.2.4-6.el7rhgs0:5.2.4-6.el7rhgs
Red Hat:storage:3.5:wa:el7rubygem-pumabefore 0:4.3.12-1.el7rhgs0:4.3.12-1.el7rhgs
Red Hat:storage:3.5:wa:el7rubygem-puma-debuginfobefore 0:4.3.12-1.el7rhgs0:4.3.12-1.el7rhgs
Red Hat:storage:3.5:wa:el7rubygem-puma-docbefore 0:4.3.12-1.el7rhgs0:4.3.12-1.el7rhgs
Red Hat:storage:3.5:wa:el7rubygem-rackbefore 0:2.2.4-1.el7rhgs0:2.2.4-1.el7rhgs
Red Hat:storage:3.5:wa:el7rubygem-rack-docbefore 0:2.2.4-1.el7rhgs0:2.2.4-1.el7rhgs
Red Hat:storage:3.5:wa:el7rubygem-tzinfobefore 0:1.2.10-1.el7rhgs0:1.2.10-1.el7rhgs
Red Hat:storage:3.5:wa:el7rubygem-tzinfo-docbefore 0:1.2.10-1.el7rhgs0:1.2.10-1.el7rhgs
RubyGemspumafrom 5.0.0 · before 5.6.45.6.4
RubyGemspumabefore 4.3.124.3.12
SUSE:HPE Helion OpenStack 8ardana-ansiblebefore 8.0+git.1660773729.3789a6d-3.85.18.0+git.1660773729.3789a6d-3.85.1
SUSE:HPE Helion OpenStack 8ardana-cobblerbefore 8.0+git.1660773402.d845a45-3.47.18.0+git.1660773402.d845a45-3.47.1
SUSE:HPE Helion OpenStack 8grafanabefore 6.7.4-4.23.16.7.4-4.23.1
SUSE:HPE Helion OpenStack 8openstack-heat-templatesbefore 0.0.0+git.1654529662.75fa04a-3.27.10.0.0+git.1654529662.75fa04a-3.27.1

+25

Same product

puma: all records

Other highest-scoring records for the same primary product.

  • CVE-2023-40175Inconsistent Interpretation of HTTP Requests in puma
    39Monitor
  • CVE-2020-11077HTTP Smuggling via Transfer-Encoding Header in Puma
    31Monitor
  • CVE-2020-11076HTTP Smuggling via Transfer-Encoding Header in Puma
    31Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2021-41136Oct 12, 2021 · Inconsistent Interpretation of HTTP Requests ('HTTP Request Smuggling') in puma
    14Monitor
  • ← EarlierCVE-2022-23634Feb 11, 2022 · Information Exposure when using Puma with Rails
    24Monitor
  • Later →CVE-2024-21647Jan 8, 2024 · HTTP Request/Response Smuggling in puma
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
puma puma5.6.4 · descriptionVendor (CNA)
debian:puma5.6.4-1 · Debian:12Package registry (OSV)
opensuse:ruby3.2-rubygem-puma-55.6.5-1.7 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:rubygem-puma4.3.12-150000.3.9.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:rubygem-puma-44.3.12-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:rubygem-puma-55.6.5-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:grafana0:5.2.4-6.el7rhgs · Red Hat:storage:3.5:wa:el7Package registry (OSV)
red hat:rubygem-puma0:4.3.12-1.el7rhgs · Red Hat:storage:3.5:wa:el7Package registry (OSV)
red hat:rubygem-puma-debuginfo0:4.3.12-1.el7rhgs · Red Hat:storage:3.5:wa:el7Package registry (OSV)
red hat:rubygem-puma-doc0:4.3.12-1.el7rhgs · Red Hat:storage:3.5:wa:el7Package registry (OSV)
red hat:rubygem-rack0:2.2.4-1.el7rhgs · Red Hat:storage:3.5:wa:el7Package registry (OSV)
red hat:rubygem-rack-doc0:2.2.4-1.el7rhgs · Red Hat:storage:3.5:wa:el7Package registry (OSV)
red hat:rubygem-tzinfo0:1.2.10-1.el7rhgs · Red Hat:storage:3.5:wa:el7Package registry (OSV)
red hat:rubygem-tzinfo-doc0:1.2.10-1.el7rhgs · Red Hat:storage:3.5:wa:el7Package registry (OSV)
red hat:tfm-rubygem-puma0:4.3.12-1.el7sat · Red Hat:satellite:6.9::el7Package registry (OSV)
red hat:tfm-rubygem-puma-debuginfo0:4.3.12-1.el7sat · Red Hat:satellite:6.9::el7Package registry (OSV)
RubyGems:puma4.3.12Package registry (OSV)
RubyGems:puma5.6.4Package registry (OSV)
suse:ardana-ansible8.0+git.1660773729.3789a6d-3.85.1 · SUSE:HPE Helion OpenStack 8Package registry (OSV)
suse:ardana-cobbler8.0+git.1660773402.d845a45-3.47.1 · SUSE:HPE Helion OpenStack 8Package registry (OSV)
suse:grafana6.7.4-4.23.1 · SUSE:HPE Helion OpenStack 8Package registry (OSV)
suse:openstack-heat-templates0.0.0+git.1654529662.75fa04a-3.27.1 · SUSE:HPE Helion OpenStack 8Package registry (OSV)
suse:openstack-murano4.0.2~dev3-3.12.1 · SUSE:HPE Helion OpenStack 8Package registry (OSV)
suse:openstack-murano-doc4.0.2~dev3-3.12.1 · SUSE:HPE Helion OpenStack 8Package registry (OSV)
suse:python-Django1.11.29-3.42.1 · SUSE:HPE Helion OpenStack 8Package registry (OSV)
suse:rabbitmq-server3.6.16-3.13.1 · SUSE:HPE Helion OpenStack 8Package registry (OSV)
suse:rubygem-puma4.3.12-150000.3.9.1 · SUSE:Linux Enterprise High Availability Extension 15Package registry (OSV)
suse:venv-openstack-heat9.0.8~dev22-12.45.1 · SUSE:HPE Helion OpenStack 8Package registry (OSV)
suse:venv-openstack-horizon12.0.5~dev6-14.48.1 · SUSE:OpenStack Cloud 8Package registry (OSV)
suse:venv-openstack-horizon-hpe12.0.5~dev6-14.48.1 · SUSE:HPE Helion OpenStack 8Package registry (OSV)

+1

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

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.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

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.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
high · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
High
Availability impact
None

Weakness class (CWE)

CWE-444 · Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records