Kernel code execution via undisclosed memory corruption
Published Feb 27, 2020 · Updated Aug 4, 2024
Memory corruption in the Apple macOS kernel in Catalina 10.15.2 allows local users to execute arbitrary code with kernel privileges. Apple has not disclosed the kernel routine, memory object, or unsafe operation that causes the corruption. Execution requires a local application and user interaction; successful exploitation crosses into kernel privilege and can fully compromise the host.
Summary
What happened
Memory corruption in the Apple macOS kernel in Catalina 10.15.2 allows local users to execute arbitrary code with kernel privileges. Apple has not disclosed the kernel routine, memory object, or unsafe operation that causes the corruption. Execution requires a local application and user interaction; successful exploitation crosses into kernel privilege and can fully compromise the host.
The record
- CVE
- CVE-2020-3871
- Published
- Feb 27, 2020
- Updated
- Aug 4, 2024
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 27, 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.3
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