Kernel code execution by local apps
Published Oct 25, 2023 · Updated Feb 13, 2025
Memory corruption in Apple Pro Res allows local users to execute arbitrary code with kernel privileges across affected iOS, iPadOS, and macOS releases. Apple identifies improper memory handling in Pro Res but has not disclosed the affected routine, input type, or precise invalid memory operation. Execution requires a user to run an app, after which successful exploitation runs attacker-controlled code in the kernel context.
Summary
What happened
Memory corruption in Apple Pro Res allows local users to execute arbitrary code with kernel privileges across affected iOS, iPadOS, and macOS releases. Apple identifies improper memory handling in Pro Res but has not disclosed the affected routine, input type, or precise invalid memory operation. Execution requires a user to run an app, after which successful exploitation runs attacker-controlled code in the kernel context.
The record
- CVE
- CVE-2023-42841
- Published
- Oct 25, 2023
- Updated
- Feb 13, 2025
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-119, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 25, 2023CVE publishedPublication date reported by the CVE source.
- Feb 13, 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.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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