Kernel code execution via graphics driver state corruption
Published Oct 28, 2021 · Updated Aug 3, 2024
Memory corruption in the Intel Graphics Driver in Apple macOS allows local users to execute arbitrary code with kernel privileges. The driver mishandles internal state in a way that corrupts memory; Apple has not disclosed the affected routine or triggering input. A malicious application must execute locally with user interaction, after which successful exploitation runs attacker-controlled code in the kernel.
Summary
What happened
Memory corruption in the Intel Graphics Driver in Apple macOS allows local users to execute arbitrary code with kernel privileges. The driver mishandles internal state in a way that corrupts memory; Apple has not disclosed the affected routine or triggering input. A malicious application must execute locally with user interaction, after which successful exploitation runs attacker-controlled code in the kernel.
The record
- CVE
- CVE-2021-30824
- Published
- Oct 28, 2021
- Updated
- Aug 3, 2024
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 28, 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 <11.6
- Affected versionversion=unspecified <12.0
- Affected versionversion=unspecified <2021
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