Sensitive data disclosure via sandbox state mishandling
Published Feb 21, 2024 · Updated Nov 4, 2025
Sandbox isolation failure in Apple iOS, iPadOS, tvOS, watchOS, and macOS allows local users to read sensitive user data. The Sandbox component mishandles security state, allowing an application to cross an intended data-access boundary; Apple has not disclosed the affected state or code path. Execution of an application on an affected device is required, and the reported consequence is limited to unauthorized access to sensitive user data.
Summary
What happened
Sandbox isolation failure in Apple iOS, iPadOS, tvOS, watchOS, and macOS allows local users to read sensitive user data. The Sandbox component mishandles security state, allowing an application to cross an intended data-access boundary; Apple has not disclosed the affected state or code path. Execution of an application on an affected device is required, and the reported consequence is limited to unauthorized access to sensitive user data.
The record
- CVE
- CVE-2023-42839
- Published
- Feb 21, 2024
- Updated
- Nov 4, 2025
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-922, T1005
- Attack vector
- local
- Privileges
- unauthenticated
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=unspecified <17.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