Kernel code execution via undisclosed validation logic
Published Sep 8, 2021 · Updated Aug 3, 2024
Kernel code execution in Apple iOS and iPadOS before 14.6 and macOS before 11.4 allows local users to gain kernel privileges. Apple identifies the locus as the kernel and attributes the flaw to deficient validation, but it has not disclosed the affected routine or invalid state. Exploitation requires a user to run a malicious application; successful execution gives that application kernel-level control.
Summary
What happened
Kernel code execution in Apple iOS and iPadOS before 14.6 and macOS before 11.4 allows local users to gain kernel privileges. Apple identifies the locus as the kernel and attributes the flaw to deficient validation, but it has not disclosed the affected routine or invalid state. Exploitation requires a user to run a malicious application; successful execution gives that application kernel-level control.
The record
- CVE
- CVE-2021-30740
- Published
- Sep 8, 2021
- Updated
- Aug 3, 2024
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 8, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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 <14.6
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.
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