Kernel code execution via out-of-bounds memory write
Published Jun 23, 2023 · Updated Dec 5, 2024
Memory corruption in the Apple macOS kernel allows local users to execute arbitrary code with kernel privileges through a malicious app. Apple has disclosed only that improved memory handling corrected the kernel issue, without identifying the faulty operation or input path. Exploitation requires a user to run an app locally; successful exploitation grants kernel-level code execution across the affected system.
Summary
What happened
Memory corruption in the Apple macOS kernel allows local users to execute arbitrary code with kernel privileges through a malicious app. Apple has disclosed only that improved memory handling corrected the kernel issue, without identifying the faulty operation or input path. Exploitation requires a user to run an app locally; successful exploitation grants kernel-level code execution across the affected system.
The record
- CVE
- CVE-2023-23516
- Published
- Jun 23, 2023
- Updated
- Dec 5, 2024
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 23, 2023CVE publishedPublication date reported by the CVE source.
- Dec 5, 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 <11.7
- Affected versionversion=unspecified <12.6
- Affected versionversion=unspecified <13.2
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.
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