A directory traversal vulnerability exists in rack < 2.2.0 that allows an attacker perform directory traversal vulnerability in the Rack::Di
Noroxi assessment
Priority: Monitor (action score 35/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: 3.3% (FIRST EPSS); higher than 88.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.
- Fixed version: ruby-rack (Debian:10) 2.0.6-3+deb10u2; ruby-rack (Debian:12) 2.1.1-5; ruby-rack (Debian:8) 1.5.2-3+deb8u3.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to ruby-rack (Debian:10) 2.0.6-3+deb10u2; ruby-rack (Debian:12) 2.1.1-5; ruby-rack (Debian:8) 1.5.2-3+deb8u3 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
A directory traversal vulnerability exists in rack < 2.2.0 that allows an attacker perform directory traversal vulnerability in the Rack::Directory app that is bundled with Rack which could result in information disclosure.
- Published
- Jul 2, 2020
- Updated
- Jun 16, 2026
- EPSS
- 3.3% · 88th percentile
- CWE
- CWE-548
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 34 / 40 · 8.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.3%
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 |
|---|---|---|
| rack project | rack | cpe:2.3:a:rack_project:rack |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canonical ubuntu linux18.04
- debian debian linux10.0
- debian debian linux9.0
- rack project rackbefore 2.2.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (hackerone). Independent of NVD's CPE analysis and usually ahead of it.
n/a https://github.com/rack/rack
- Fixed in 2.1.3, >= 2.2.0affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:10 | ruby-rack | before 2.0.6-3+deb10u2 | 2.0.6-3+deb10u2 |
| Debian:12 | ruby-rack | before 2.1.1-5 | 2.1.1-5 |
| Debian:8 | ruby-rack | before 1.5.2-3+deb8u3 | 1.5.2-3+deb8u3 |
| Debian:9 | ruby-rack | before 1.6.4-4+deb9u2 | 1.6.4-4+deb9u2 |
| RubyGems | rack | before 2.1.3 | 2.1.3 |
| SUSE:Linux Enterprise High Availability Extension 15 | rubygem-rack | before 2.0.8-150000.3.9.1 | 2.0.8-150000.3.9.1 |
| SUSE:Linux Enterprise High Availability Extension 15 | rubygem-rack | before 2.0.8-150000.3.9.1 | 2.0.8-150000.3.9.1 |
| SUSE:OpenStack Cloud 7 | rubygem-rack | before 1.6.13-3.8.1 | 1.6.13-3.8.1 |
Same product
rack project: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-30123A sequence injection vulnerability exists in Rack <2.0.9.1, <2.1.4.1 and <2.2.3.1 which could allow is a possible shell escape in the Lint a41Plan
- CVE-2022-30122A possible denial of service vulnerability exists in Rack <2.0.9.1, <2.1.4.1 and <2.2.3.1 in the multipart parsing component of Rack.31Monitor
- CVE-2020-8184A reliance on cookies without validation/integrity check security vulnerability exists in rack < 2.2.3, rack < 2.1.4 that makes it is possib31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2015-3225Jul 26, 2015 · lib/rack/utils.rb in Rack before 1.5.4 and 1.6.x before 1.6.2, as used with Ruby on Rails 3.x and 4.x and other products, allows remote atta22Monitor
- ← EarlierCVE-2018-16470Nov 13, 2018 · There is a possible DoS vulnerability in the multipart parser in Rack before 2.0.6.31Monitor
- ← EarlierCVE-2018-16471Nov 13, 2018 · There is a possible XSS vulnerability in Rack before 2.0.6 and 1.6.11.25Monitor
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:ruby-rack | 2.1.1-5 · Debian:12 | Package registry (OSV) |
| opensuse:rubygem-rack | 2.0.8-150000.3.9.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| RubyGems:rack | 2.1.3 | Package registry (OSV) |
| suse:rubygem-rack | 1.6.13-3.8.1 · SUSE:OpenStack Cloud 7 | Package registry (OSV) |
| suse:rubygem-rack | 2.0.8-150000.3.9.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.
No commit or PR link among the references.
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
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-20-385 · May 27, 2020(Ruby Güvenlik Güncellemesi)
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
- high · data can be read
- Integrity
- none
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-548 · Exposure of Information Through Directory ListingCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.