CVE-2022-23634
Information Exposure when using Puma with Rails
Public exploit available. Not confirmed exploited in the wild yet. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- RubyGems pumaAffected: ≥ 5.0.0, < 5.6.2Upgrade to: 5.6.2Stated by: GitHub advisory
- PumaAffected: < 4.3.11Upgrade to: 4.3.11Stated by: NVD
- Rubyonrails RailsAffected: ≥ 5.0.0, < 5.2.6.2Upgrade to: 5.2.6.2Stated by: NVD
- Сообщество свободного программного обеспечения Debian GNU/LinuxAffected: 9Upgrade to: not statedStated by: BDU
- Canonical Ltd. UbuntuAffected: 20.04 LTSUpgrade to: not statedStated by: BDU
Versions as the sources state them. 4 more products have version data. Full version matrix after sign-in
What it is
From the CVE record
Puma is a Ruby/Rack web server built for parallelism. Prior to `puma` version `5.6.2`, `puma` may not always call `close` on the response body. Rails, prior to version `7.0.2.2`, depended on the response body being closed in order for its `CurrentAttributes` implementation to work correctly. The combination of these two behaviors (Puma not closing the body + Rails' Executor implementation) causes information leakage. This problem is fixed in Puma versions 5.6.2 and 4.3.11. This problem is fixed in Rails versions 7.02.2, 6.1.4.6, 6.0.4.6, and 5.2.6.2. Upgrading to a patched Rails _or_ Puma version fixes the vulnerability.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
1 source with a proof of concept or module.
Exploit links, PoCs and Metasploit modules after sign-in- EPSS
2.1% chance of exploitation activity in the next 30 days, which ranks it in the 82nd percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
The patch came 471 days before any public exploit.
- OpenVAS check added
- Public exploit / PoCsource: github-poc
- Patch availableworkaround available, record updated
- Publishedweakness classified, att&ck mapped
Affected products
And 4 more affected products. See all after sign-in
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N
Scored 8.0 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction RequiredA user must click a link, open a file, or perform some action
Scope
- Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)
Impact if exploited
- Confidentiality HighTotal information disclosure — all data in the component is compromised
- Integrity HighTotal loss of integrity — attacker can modify any data in the component
- Availability NoneNo availability impact
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
Sources
References in the record
- github.com/advisories/GHSA-rmj8-8hhh-gv5h
- github.com/advisories/GHSA-wh98-p28r-vrc9
- github.com/puma/puma/commit/b70f451fe8abc0cff192c065d549778452e155bb
And 21 more references. See all after sign-in
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Debian GNU/Linux, not every advisory. This one: public exploit.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI