Kernel code execution via graphics-driver out-of-bounds write
Published Apr 2, 2021 · Updated Aug 4, 2024
Out-of-bounds write in Apple macOS before 11.1 allows local users to execute arbitrary code with kernel privileges via a malicious application. The Graphics Drivers component writes beyond an allocated buffer when processing attacker-controlled graphics input because input bounds are not adequately validated. Exploitation requires a local application to run on the Mac, after which kernel-level code execution can compromise confidentiality, integrity, and availability.
Summary
What happened
Out-of-bounds write in Apple macOS before 11.1 allows local users to execute arbitrary code with kernel privileges via a malicious application. The Graphics Drivers component writes beyond an allocated buffer when processing attacker-controlled graphics input because input bounds are not adequately validated. Exploitation requires a local application to run on the Mac, after which kernel-level code execution can compromise confidentiality, integrity, and availability.
The record
- CVE
- CVE-2020-27947
- Published
- Apr 2, 2021
- Updated
- Aug 4, 2024
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 2, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.1
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