Kernel code execution via memory corruption
Published Apr 1, 2020 · Updated Aug 4, 2024
Memory corruption in Apple operating systems before the listed fixes allows a malicious application to execute arbitrary code with kernel privileges. Apple describes multiple state-management memory corruptions but does not publish a specific component or function locus for CVE-2020-9785. Exploitation requires local application execution and user interaction to launch the malicious application; the resulting impact is kernel-level code execution affecting confidentiality, integrity, and availability.
Summary
What happened
Memory corruption in Apple operating systems before the listed fixes allows a malicious application to execute arbitrary code with kernel privileges. Apple describes multiple state-management memory corruptions but does not publish a specific component or function locus for CVE-2020-9785. Exploitation requires local application execution and user interaction to launch the malicious application; the resulting impact is kernel-level code execution affecting confidentiality, integrity, and availability.
The record
- CVE
- CVE-2020-9785
- Published
- Apr 1, 2020
- Updated
- Aug 4, 2024
- Vendor
- Apple
- Product
- iOS
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
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 <iOS 13.4 and iPadOS 13.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