Arbitrary root file overwrite via card labels
Published Jan 30, 2020 · Updated Aug 6, 2024
Path traversal in OpenSC.tokend before 0.13.0 allows physically proximate attackers to overwrite files as root via a smart card. The token cache code concatenates untrusted card and token labels into paths beneath /var/db/TokenCache and follows symbolic links instead of hashing those values. Insertion of a crafted or relabeled card into a macOS reader is required; the root process can corrupt directories or files even while the screen is locked.
Summary
What happened
Path traversal in OpenSC.tokend before 0.13.0 allows physically proximate attackers to overwrite files as root via a smart card. The token cache code concatenates untrusted card and token labels into paths beneath /var/db/TokenCache and follows symbolic links instead of hashing those values. Insertion of a crafted or relabeled card into a macOS reader is required; the root process can corrupt directories or files even while the screen is locked.
The record
- CVE
- CVE-2013-1866
- Published
- Jan 30, 2020
- Updated
- Aug 6, 2024
- Vendor
- OpenSC Project
- Product
- OpenSC.tokend
- Classifications
- CWE-59, T1200
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 30, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 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=2013
What conditions does exploitation require?
What is affected?
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