Local kernel code execution via memory corruption
Published Apr 1, 2020 · Updated Aug 4, 2024
Memory corruption in AppleGraphicsControl in Apple macOS before Catalina 10.15.4 allows local users to execute code with kernel privileges. Apple reports that multiple state-management flaws corrupt memory in AppleGraphicsControl but has not disclosed the exact operations or inputs involved. A malicious application must already run locally; successful exploitation grants kernel-level control over the system.
Summary
What happened
Memory corruption in AppleGraphicsControl in Apple macOS before Catalina 10.15.4 allows local users to execute code with kernel privileges. Apple reports that multiple state-management flaws corrupt memory in AppleGraphicsControl but has not disclosed the exact operations or inputs involved. A malicious application must already run locally; successful exploitation grants kernel-level control over the system.
The record
- CVE
- CVE-2020-3904
- Published
- Apr 1, 2020
- Updated
- Aug 4, 2024
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 1, 2020CVE 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 <macOS Catalina 10.15.4
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