Arbitrary file write via symlinked archive paths
Published Oct 28, 2021 · Updated Aug 3, 2024
Path traversal in Apple macOS before 12.0 allows context-dependent attackers to write arbitrary files through a crafted XAR archive. The xar utility accepts a slash-separated file name beneath an archived directory symlink and resolves extraction through that symlink outside the destination. A user must extract the archive, and writes are limited to locations permitted by that user's filesystem access.
Summary
What happened
Path traversal in Apple macOS before 12.0 allows context-dependent attackers to write arbitrary files through a crafted XAR archive. The xar utility accepts a slash-separated file name beneath an archived directory symlink and resolves extraction through that symlink outside the destination. A user must extract the archive, and writes are limited to locations permitted by that user's filesystem access.
The record
- CVE
- CVE-2021-30833
- Published
- Oct 28, 2021
- Updated
- Aug 3, 2024
- Vendor
- Apple
- Product
- macOS
- Classifications
- T1204.002
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 28, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=unspecified <12.0
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
- NCC Group XAR 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