CVE-2022-23634
No exploitation reported by the sources we read.
- Published2022-02-11
- Fixed in5.6.2 · 4.3.11
- WeaknessCWE-200 · CWE-404
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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.
Timeline
dates in UTC- 2022-02-1122:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2022-23634?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2022-23634?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD · OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 5.x | ≥ 5.0.0, < 5.6.2 | 5.6.2 | NVD · OSV |
| 4.3 | < 4.3.11 | 4.3.11 | NVD · OSV |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 7.0 | ≥ 7.0.0, < 7.0.2.2 | 7.0.2.2 | NVD |
| 6.1 | ≥ 6.1.0, < 6.1.4.6 | 6.1.4.6 | NVD |
| 6.0 | ≥ 6.0.0, < 6.0.4.6 | 6.0.4.6 | NVD |
| 5.x | ≥ 5.0.0, < 5.2.6.2 | 5.2.6.2 | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 9.0 | = 9.0 | no fix published | NVD |
| 10.0 | = 10.0 | no fix published | NVD |
| 11.0 | = 11.0 | no fix published | NVD |
1 more product in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Puma to 5.6.2 · 4.3.11
Advisories and patches
- github.comMitigation
- github.comPatch
- github.comPatch
- groups.google.comMitigation · Patch
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- Published
- 2022-02-11
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2022-23634?
Is CVE-2022-23634 actively exploited?
What is the CVSS score for CVE-2022-23634?
Running puma? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.