Kernel code execution via graphics driver bounds error
Published Sep 8, 2021 · Updated Aug 3, 2024
Out-of-bounds write in macOS before 11.3 allows local users to execute arbitrary code with kernel privileges via a malicious application. The Intel Graphics Driver fails to enforce bounds when handling crafted input, allowing writes beyond the intended buffer. Exploitation requires execution of a malicious application on the Mac and can compromise kernel confidentiality, integrity, and availability.
Summary
What happened
Out-of-bounds write in macOS before 11.3 allows local users to execute arbitrary code with kernel privileges via a malicious application. The Intel Graphics Driver fails to enforce bounds when handling crafted input, allowing writes beyond the intended buffer. Exploitation requires execution of a malicious application on the Mac and can compromise kernel confidentiality, integrity, and availability.
The record
- CVE
- CVE-2021-1841
- Published
- Sep 8, 2021
- Updated
- Aug 3, 2024
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-787, 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 <11.3
- 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