Kernel code execution via undisclosed memory-handling flaw
Published Jul 27, 2023 · Updated Oct 23, 2024
A kernel memory-handling flaw in iOS and iPadOS before 16.6 and macOS Ventura before 13.5 allows attackers to execute kernel code via an app. Apple identifies the locus only as Kernel and says improved memory handling resolved the issue, without disclosing the faulty operation or input. Exploitation requires a user to run an app, after which the app can cross its existing privilege boundary and execute arbitrary code in the kernel.
Summary
What happened
A kernel memory-handling flaw in iOS and iPadOS before 16.6 and macOS Ventura before 13.5 allows attackers to execute kernel code via an app. Apple identifies the locus only as Kernel and says improved memory handling resolved the issue, without disclosing the faulty operation or input. Exploitation requires a user to run an app, after which the app can cross its existing privilege boundary and execute arbitrary code in the kernel.
The record
- CVE
- CVE-2023-38424
- Published
- Jul 27, 2023
- Updated
- Oct 23, 2024
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- T1068, T1404
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 27, 2023CVE publishedPublication date reported by the CVE source.
- Oct 23, 2024Record 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.6
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