Arbitrary file reads via unchecked debug paths
Published Dec 26, 2021 · Updated Aug 4, 2024
Path traversal in rust-embed before 6.3.0 allows attackers to read arbitrary files through crafted paths in debug-mode applications. The generated get method reads a supplied path without verifying that it remains beneath the configured asset folder. Exploitation requires a debug build without the debug-embed feature and a caller that passes an attacker-controlled filename.
Summary
What happened
Path traversal in rust-embed before 6.3.0 allows attackers to read arbitrary files through crafted paths in debug-mode applications. The generated get method reads a supplied path without verifying that it remains beneath the configured asset folder. Exploitation requires a debug build without the debug-embed feature and a caller that passes an attacker-controlled filename.
The record
- CVE
- CVE-2021-45712
- Published
- Dec 26, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-22, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 26, 2021CVE 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- RustSec directory-traversal proof of conceptproof of concept · demonstrated
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