Kernel code execution via corrupt state management
Published Jun 9, 2020 · Updated Aug 4, 2024
Kernel memory corruption in Apple iOS, macOS, tvOS, and watchOS allows local users to execute arbitrary code with kernel privileges. The kernel's state-management logic enters a corrupt memory state while processing operations from a malicious application; Apple has not disclosed the specific function or input. Execution requires a malicious application to run locally and grants control at kernel privilege across the affected device.
Summary
What happened
Kernel memory corruption in Apple iOS, macOS, tvOS, and watchOS allows local users to execute arbitrary code with kernel privileges. The kernel's state-management logic enters a corrupt memory state while processing operations from a malicious application; Apple has not disclosed the specific function or input. Execution requires a malicious application to run locally and grants control at kernel privilege across the affected device.
The record
- CVE
- CVE-2020-9813
- Published
- Jun 9, 2020
- Updated
- Aug 4, 2024
- Vendor
- Apple
- Product
- iOS
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 9, 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.5 and iPadOS 13.5
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