Kernel code execution via out-of-bounds read
Published Jul 28, 2023 · Updated Feb 13, 2025
Out-of-bounds read in Apple operating-system kernels allows local users running a crafted app to execute code with kernel privileges. Apple identifies the locus only as Kernel and states that affected builds fail to enforce bounds before a read; no narrower code path is public. The attacker must first run an app on the device, after which successful exploitation grants kernel-level code execution.
Summary
What happened
Out-of-bounds read in Apple operating-system kernels allows local users running a crafted app to execute code with kernel privileges. Apple identifies the locus only as Kernel and states that affected builds fail to enforce bounds before a read; no narrower code path is public. The attacker must first run an app on the device, after which successful exploitation grants kernel-level code execution.
The record
- CVE
- CVE-2023-37285
- Published
- Jul 28, 2023
- Updated
- Feb 13, 2025
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-125, T1068
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jul 28, 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 <15.7
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