Arbitrary file write via archive extraction race
Published Sep 16, 2024 · Updated Apr 2, 2026
Arbitrary file write in Apple Compression on affected iOS, iPadOS, macOS, and visionOS releases allows attackers to abuse archive extraction. In libAppleArchive's concatExtractPath(), concurrent extraction creates a symlink after lstat64 but before mkdir, whose failure is ignored before the file write. A user must unpack the crafted archive; the write follows the symlink to a path reachable within the extracting process's sandbox.
Summary
What happened
Arbitrary file write in Apple Compression on affected iOS, iPadOS, macOS, and visionOS releases allows attackers to abuse archive extraction. In libAppleArchive's concatExtractPath(), concurrent extraction creates a symlink after lstat64 but before mkdir, whose failure is ignored before the file write. A user must unpack the crafted archive; the write follows the symlink to a path reachable within the extracting process's sandbox.
The record
- CVE
- CVE-2024-27876
- Published
- Sep 16, 2024
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- iOS
- Classifications
- CWE-362, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 16, 2024CVE publishedPublication date reported by the CVE source.
- Apr 2, 2026Record 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=0 <17.7
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
- libAppleArchive exploit makerproof 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