Sandbox escape via quarantine access control flaw
Published Feb 21, 2024 · Updated Nov 4, 2025
Improper access control in macOS quarantine allows local users to execute code outside an app sandbox or with elevated privileges. The quarantine component applies an undisclosed, incorrect access decision to a sandboxed app; Apple has not identified the affected operation or input. Exploitation requires a user to run an app on an affected Mac, after which code can escape that app's sandbox or gain privileges.
Summary
What happened
Improper access control in macOS quarantine allows local users to execute code outside an app sandbox or with elevated privileges. The quarantine component applies an undisclosed, incorrect access decision to a sandboxed app; Apple has not identified the affected operation or input. Exploitation requires a user to run an app on an affected Mac, after which code can escape that app's sandbox or gain privileges.
The record
- CVE
- CVE-2023-42838
- Published
- Feb 21, 2024
- Updated
- Nov 4, 2025
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-284, T1068
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Feb 21, 2024CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record 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 <12.7.2
- Affected versionversion=13.0 <13.6.3
- Affected versionversion=14.0 <14.1
- Affected versionversion=unspecified <12.7
- Affected versionversion=unspecified <13.6
- Affected versionversion=unspecified <14.1
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