CVE-2016-2097
Last modified
CVE-2016-2097 is a vulnerability of currently unknown severity. Directory traversal vulnerability in Action View in Ruby on Rails before 3.2.22.2 and 4.x before 4.1.14.2 allows remote attackers to read arbitrary files by leveraging an application's unrestricted use of the render method and providing a .. (dot dot) in a pathname. EPSS estimates a 4.42% chance of exploitation in the next 30 days.
Description
Directory traversal vulnerability in Action View in Ruby on Rails before 3.2.22.2 and 4.x before 4.1.14.2 allows remote attackers to read arbitrary files by leveraging an application's unrestricted use of the render method and providing a .. (dot dot) in a pathname. NOTE: this vulnerability exists because of an incomplete fix for CVE-2016-0752.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Rubyonrails | Rails | 4.0.0 | — |
| Rubyonrails | Rails | 4.0.1 | — |
| Rubyonrails | Rails | 4.0.2 | — |
| Rubyonrails | Rails | 4.0.3 | — |
| Rubyonrails | Rails | 4.0.4 | — |
| Rubyonrails | Rails | 4.0.5 | — |
| Rubyonrails | Rails | 4.0.6 | — |
| Rubyonrails | Rails | 4.0.7 | — |
| Rubyonrails | Rails | 4.0.8 | — |
| Rubyonrails | Rails | 4.0.9 | — |
| Rubyonrails | Rails | 4.0.10 | Rc1 |
| Rubyonrails | Rails | 4.1.0 | — |
| Rubyonrails | Rails | 4.1.1 | — |
| Rubyonrails | Rails | 4.1.2 | — |
| Rubyonrails | Rails | 4.1.3 | — |
| Rubyonrails | Rails | 4.1.4 | — |
| Rubyonrails | Rails | 4.1.5 | — |
| Rubyonrails | Rails | 4.1.6 | Rc1 |
| Rubyonrails | Rails | 4.1.7 | — |
| Rubyonrails | Rails | 4.1.7.1 | — |
| Rubyonrails | Rails | 4.1.8 | — |
| Rubyonrails | Rails | 4.1.9 | Rc1 |
| Rubyonrails | Rails | 4.1.10 | Rc1 |
| Rubyonrails | Rails | 4.1.12 | Rc1 |
| Rubyonrails | Rails | 4.1.13 | Rc1 |
| Rubyonrails | Rails | 4.1.14 | Rc1 |
| Rubyonrails | Ruby On Rails | <= 3.2.22.1 | — |
| Rubyonrails | Ruby On Rails | 4.1.14.1 | — |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2016-2097?
How severe is CVE-2016-2097?
How do I fix CVE-2016-2097?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2016
- CVE-2016-2087Directory traversal vulnerability in the client in HexChat 2…
- CVE-2016-2088resolver.c in named in ISC BIND 9.10.x before 9.10.3-P4, whe…
- CVE-2016-2089The jas_matrix_clip function in jas_seq.c in JasPer 1.900.1 …
- CVE-2016-2090Off-by-one vulnerability in the fgetwln function in libbsd b…9.8
- CVE-2016-2091The dwarf_read_cie_fde_prefix function in dwarf_frame2.c in …3.3
- CVE-2016-2094The HTTPS NIO Connector allows remote attackers to cause a d…
- CVE-2016-2098Action Pack in Ruby on Rails before 3.2.22.2, 4.x before 4.1…
- CVE-2016-2099Use-after-free vulnerability in validators/DTD/DTDScanner.cp…
- CVE-2016-2100Foreman before 1.10.3 and 1.11.0 before 1.11.0-RC2 allow rem…
- CVE-2016-2101Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2016-2102HAProxy statistics in openstack-tripleo-image-elements are n…
- CVE-2016-2103Multiple cross-site scripting (XSS) vulnerabilities in Red H…
Are you affected by CVE-2016-2097?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST