Kernel code execution via IOGraphics memory corruption
Published Oct 28, 2021 · Updated Aug 3, 2024
IOGraphics memory corruption in affected Apple macOS releases allows local users to execute kernel code via a malicious application. Apple identifies improper memory handling in IOGraphics but has not published the affected code path, memory-safety operation, or triggering input. A malicious application must run locally on an affected Mac; successful corruption grants kernel-level code execution on Catalina before Security Update 2021-007, Big Sur before 11.6.1, and Monterey before 12.0.1.
Summary
What happened
IOGraphics memory corruption in affected Apple macOS releases allows local users to execute kernel code via a malicious application. Apple identifies improper memory handling in IOGraphics but has not published the affected code path, memory-safety operation, or triggering input. A malicious application must run locally on an affected Mac; successful corruption grants kernel-level code execution on Catalina before Security Update 2021-007, Big Sur before 11.6.1, and Monterey before 12.0.1.
The record
- CVE
- CVE-2021-30821
- Published
- Oct 28, 2021
- Updated
- Aug 3, 2024
- Vendor
- Apple
- Product
- macOS
- Classifications
- 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.
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