Arbitrary file write via cache path traversal
Published May 12, 2020 · Updated Aug 4, 2024
Path traversal in Ruby on Rails Action Pack Page Caching before 1.2.1 allows remote attackers to write server files via crafted URLs. The cache_path method joined a request-derived cache filename to the cache directory without normalizing the result or verifying that it remained beneath that directory. A Rails action must use caches_page and caching must be enabled; code execution requires an attacker-controlled response body to be stored as unescaped ERB in a view directory.
Summary
What happened
Path traversal in Ruby on Rails Action Pack Page Caching before 1.2.1 allows remote attackers to write server files via crafted URLs. The cache_path method joined a request-derived cache filename to the cache directory without normalizing the result or verifying that it remained beneath that directory. A Rails action must use caches_page and caching must be enabled; code execution requires an attacker-controlled response body to be stored as unescaped ERB in a view directory.
The record
- CVE
- CVE-2020-8159
- Published
- May 12, 2020
- Updated
- Aug 4, 2024
- Vendor
- Ruby on Rails
- Product
- Action Pack Page Caching
- Classifications
- CWE-22, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 12, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=v1.2.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo