Kernel code execution via out-of-bounds write
Published Feb 27, 2023 · Updated Mar 11, 2025
Memory corruption in the Kernel component of affected Apple platforms allows local users to execute arbitrary code with kernel privileges. Apple identifies deficient memory handling, while CISA-ADP maps the flaw to an out-of-bounds write; no affected kernel routine is public. Exploitation requires a user to run an app on an affected device, after which the app gains kernel-level control.
Summary
What happened
Memory corruption in the Kernel component of affected Apple platforms allows local users to execute arbitrary code with kernel privileges. Apple identifies deficient memory handling, while CISA-ADP maps the flaw to an out-of-bounds write; no affected kernel routine is public. Exploitation requires a user to run an app on an affected device, after which the app gains kernel-level control.
The record
- CVE
- CVE-2023-23504
- Published
- Feb 27, 2023
- Updated
- Mar 11, 2025
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 27, 2023CVE publishedPublication date reported by the CVE source.
- Mar 11, 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 <15.7
- Affected versionversion=unspecified <16.3
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.
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