Kernel code execution from root-privileged apps
Published May 8, 2023 · Updated Jan 29, 2025
Memory corruption in Apple operating systems before their March 2023 updates allows local users to execute code with kernel privileges. Apple identifies the Kernel component and improper memory handling, but has not disclosed the affected object or erroneous operation. Exploitation requires a root-privileged app already running locally, and success crosses the user-kernel boundary to kernel code execution.
Summary
What happened
Memory corruption in Apple operating systems before their March 2023 updates allows local users to execute code with kernel privileges. Apple identifies the Kernel component and improper memory handling, but has not disclosed the affected object or erroneous operation. Exploitation requires a root-privileged app already running locally, and success crosses the user-kernel boundary to kernel code execution.
The record
- CVE
- CVE-2023-27933
- Published
- May 8, 2023
- Updated
- Jan 29, 2025
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 8, 2023CVE publishedPublication date reported by the CVE source.
- Jan 29, 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.4
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