Local file disclosure via slash-bearing readdir names
Published Dec 5, 2024 · Updated Dec 5, 2024
Path traversal in OpenBSD 7.4 before errata 022 and 7.5 before errata 009 allows local users to read files via an untrusted file system. The readdir name validator fails to reject slash characters in directory-entry names, allowing one entry to be interpreted as multiple path components. Reaching the flaw requires low-privileged local access, active user interaction, and a controllable untrusted file system; the published impact is file disclosure only.
Summary
What happened
Path traversal in OpenBSD 7.4 before errata 022 and 7.5 before errata 009 allows local users to read files via an untrusted file system. The readdir name validator fails to reject slash characters in directory-entry names, allowing one entry to be interpreted as multiple path components. Reaching the flaw requires low-privileged local access, active user interaction, and a controllable untrusted file system; the published impact is file disclosure only.
The record
- CVE
- CVE-2024-10933
- Published
- Dec 5, 2024
- Updated
- Dec 5, 2024
- Vendor
- OpenBSD Project
- Product
- OpenBSD
- Classifications
- CWE-22, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 5, 2024CVE publishedPublication date reported by the CVE source.
- Dec 5, 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=7.4 <7.4 errata 022
- Affected versionversion=7.5 <7.5 errata 009
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