Exposure of sensitive information in Action Pack
Noroxi assessment
Priority: Monitor (action score 24/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.2% (FIRST EPSS); higher than 82.4% 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: rails (Debian:10) 2:5.2.2.1+dfsg-1+deb10u4; rails (Debian:11) 2:6.0.3.7+dfsg-2+deb11u1; rails (Debian:12) 2:6.1.4.6+dfsg-1.
Low priority for now. Upgrade to rails (Debian:10) 2:5.2.2.1+dfsg-1+deb10u4; rails (Debian:11) 2:6.0.3.7+dfsg-2+deb11u1; rails (Debian:12) 2:6.1.4.6+dfsg-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
Action Pack is a framework for handling and responding to web requests. Under certain circumstances response bodies will not be closed. In the event a response is *not* notified of a `close`, `ActionDispatch::Executor` will not know to reset thread local state for the next request. This can lead to data being leaked to subsequent requests.This has been fixed in Rails 7.0.2.1, 6.1.4.5, 6.0.4.5, and 5.2.6.1. Upgrading is highly recommended, but to work around this problem a middleware described in GHSA-wh98-p28r-vrc9 can be used.
- Published
- Feb 11, 2022
- Updated
- Jun 17, 2026
- EPSS
- 2.2% · 82th percentile
- CWE
- CWE-200
Report tools
Action score
24
Monitor
Low priority for now.
- CVSS
- 23 / 40 · 5.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.2%
CNA vs NVD score
- NVD
- 5.9
- CNA · GitHub_M
- 7.4
- 1.5 point gap
CVSS:3.1/AV:N/AC:H/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.
Running WordPress? Scan your site free with WP Lens
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 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 |
|---|---|---|
| rubyonrails | rails | cpe:2.3:a:rubyonrails:rails |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
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
- rubyonrails rails5.0.0 and later · before 5.2.6.2
- rubyonrails rails6.0.0 and later · before 6.0.4.6
- rubyonrails rails6.1.0 and later · before 6.1.4.6
- rubyonrails rails7.0.0 and later · before 7.0.2.2
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.
rails rails
- >= 7.0.0.0, < 7.0.2.1, >= 6.1.0.0, < 6.1.4.5, >= 6.0.0.0, < 6.0.4.5, >= 5.0.0, < 5.2.6.1affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:10 | rails | before 2:5.2.2.1+dfsg-1+deb10u4 | 2:5.2.2.1+dfsg-1+deb10u4 |
| Debian:11 | rails | before 2:6.0.3.7+dfsg-2+deb11u1 | 2:6.0.3.7+dfsg-2+deb11u1 |
| Debian:12 | rails | before 2:6.1.4.6+dfsg-1 | 2:6.1.4.6+dfsg-1 |
| openSUSE:Tumbleweed | ruby3.2-rubygem-actionpack-7.0 | before 7.0.4.3-1.1 | 7.0.4.3-1.1 |
| openSUSE:Tumbleweed | rubygem-actionpack-6.0 | before 6.0.4.6-1.1 | 6.0.4.6-1.1 |
| openSUSE:Tumbleweed | rubygem-actionpack-7.0 | before 7.0.8.4-1.1 | 7.0.8.4-1.1 |
| openSUSE:Tumbleweed | rubygem-actionpack-7.0 | before 7.0.8.6-1.3 | 7.0.8.6-1.3 |
| openSUSE:Tumbleweed | rubygem-actionpack-7.0 | before 7.0.2.2-1.1 | 7.0.2.2-1.1 |
| RubyGems | actionpack | from 5.0.0.0 · before 5.2.6.2 | 5.2.6.2 |
| RubyGems | actionpack | from 6.0.0.0 · before 6.0.4.6 | 6.0.4.6 |
| RubyGems | actionpack | from 6.1.0.0 · before 6.1.4.6 | 6.1.4.6 |
| RubyGems | actionpack | from 7.0.0.0 · before 7.0.2.2 | 7.0.2.2 |
| SUSE:Linux Enterprise High Availability Extension 15 | rubygem-actionpack-5_1 | before 5.1.4-150000.3.12.1 | 5.1.4-150000.3.12.1 |
| SUSE:Linux Enterprise High Availability Extension 15 | rubygem-actionpack-5_1 | before 5.1.4-150000.3.12.1 | 5.1.4-150000.3.12.1 |
| SUSE:Linux Enterprise High Availability Extension 15 | rubygem-activesupport-5_1 | before 5.1.4-150000.3.6.1 | 5.1.4-150000.3.6.1 |
| SUSE:Linux Enterprise High Availability Extension 15 | rubygem-activesupport-5_1 | before 5.1.4-150000.3.6.1 | 5.1.4-150000.3.6.1 |
Same product
rubyonrails: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-5418There is a File Content Disclosure vulnerability in Action View <5.2.2.1, <5.1.6.2, <5.0.7.2, <4.2.11.1 and v3 where specially crafted accepKEV90Now
- CVE-2016-0752Directory traversal vulnerability in Action View in Ruby on Rails before 3.2.22.1, 4.0.x and 4.1.x before 4.1.14.1, 4.2.x before 4.2.5.1, anKEV89Now
- CVE-2019-5420A remote code execution vulnerability in development mode Rails <5.2.2.1, <6.0.0.beta3 can allow an attacker to guess the automatically gene66This week
Published before and after this one in the same product
- ← EarlierCVE-2011-1497Oct 19, 2021 · A cross-site scripting vulnerability flaw was found in the auto_link function in Rails before version 3.0.6.24Monitor
- ← EarlierCVE-2021-44528Jan 10, 2022 · A open redirect vulnerability exists in Action Pack >= 6.0.0 that could allow an attacker to craft a "X-Forwarded-Host" headers in combinati25Monitor
- Later →CVE-2022-3704Oct 26, 2022 · Ruby on Rails _table.html.erb cross site scripting21Monitor
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:rails | 2:6.1.4.6+dfsg-1 · Debian:12 | Package registry (OSV) |
| opensuse:ruby3.2-rubygem-actionpack-7.0 | 7.0.4.3-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:rubygem-actionpack-5_1 | 5.1.4-150000.3.12.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| opensuse:rubygem-actionpack-6.0 | 6.0.4.6-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:rubygem-actionpack-7.0 | 7.0.2.2-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:rubygem-activesupport-5_1 | 5.1.4-150000.3.6.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| RubyGems:actionpack | 5.2.6.2 | Package registry (OSV) |
| RubyGems:actionpack | 6.0.4.6 | Package registry (OSV) |
| RubyGems:actionpack | 6.1.4.6 | Package registry (OSV) |
| RubyGems:actionpack | 7.0.2.2 | Package registry (OSV) |
| suse:rubygem-actionpack-5_1 | 5.1.4-150000.3.12.1 · SUSE:Linux Enterprise High Availability Extension 15 | Package registry (OSV) |
| suse:rubygem-activesupport-5_1 | 5.1.4-150000.3.6.1 · SUSE:Linux Enterprise High Availability Extension 15 | Package registry (OSV) |
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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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 researchersFinders, 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
The product’s vendor appears in a public program. Matched by name; verify the scope text in the 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
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-200 · Exposure of Sensitive Information to an Unauthorized ActorCVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Root cause
The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.
The bug in code
The whole CWE-200 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
{ "permissions": ["tabs", "<all_urls>"], "background": { "service_worker": "analytics.js" }}Fixed
{ "permissions": ["activeTab"], "host_permissions": ["https://yildiz.example/*"]}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- ExcavationCAPEC-116likelihood: High · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
- FootprintingCAPEC-169likelihood: High · Very Low
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- FingerprintingCAPEC-224likelihood: High · Very Low
- ICMP Echo Request PingCAPEC-285likelihood: Medium · Low
- TCP SYN ScanCAPEC-287Low
- Enumerate Mail Exchange (MX) RecordsCAPEC-290Low
ATT&CK techniques
- System Service DiscoveryT1007
- System Network Configuration DiscoveryT1016
- Remote System DiscoveryT1018
- System Owner/User DiscoveryT1033
- Masquerading: Match Legitimate Name or LocationT1036.005
- Network Service ScanningT1046
- System Network Connections DiscoveryT1049
- Process DiscoveryT1057
- Permission Groups DiscoveryT1069
- System Information DiscoveryT1082
- File and Directory DiscoveryT1083
- Account DiscoveryT1087
- Multi-Factor Authentication InterceptionT1111
- Peripheral Device DiscoveryT1120
- System Time DiscoveryT1124
- Access Token Manipulation:Token Impersonation/TheftT1134.001
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.