Protected user data access via Libsystem permissions
Published Mar 28, 2024 · Updated Nov 4, 2025
A permissions flaw in Apple Libsystem on affected macOS, iOS, iPadOS, tvOS, and watchOS releases allows local users to access protected user data. Apple identifies Libsystem as the locus but has not disclosed which permission check was missing or how untrusted input reaches the removed code. Exploitation requires local execution and user interaction, and the documented consequence is unauthorized reading of protected user data without integrity or availability impact.
Summary
What happened
A permissions flaw in Apple Libsystem on affected macOS, iOS, iPadOS, tvOS, and watchOS releases allows local users to access protected user data. Apple identifies Libsystem as the locus but has not disclosed which permission check was missing or how untrusted input reaches the removed code. Exploitation requires local execution and user interaction, and the documented consequence is unauthorized reading of protected user data without integrity or availability impact.
The record
- CVE
- CVE-2023-42893
- Published
- Mar 28, 2024
- Updated
- Nov 4, 2025
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 28, 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 <16.7
- Affected versionversion=unspecified <17.2
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
No sourced classifications are available.
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