Kernel code execution via improper memory initialization
Published Apr 1, 2020 · Updated Aug 4, 2024
Improper initialization in Apple IOHIDFamily before iOS 13.4, macOS 10.15.4, tvOS 13.4, and watchOS 6.2 allows local users to execute kernel code. The IOHIDFamily component initializes memory incorrectly; Apple has not published the affected function, data structure, or input path. Exploitation requires a malicious application to run locally and grants kernel privileges, placing the affected device under application-controlled kernel code.
Summary
What happened
Improper initialization in Apple IOHIDFamily before iOS 13.4, macOS 10.15.4, tvOS 13.4, and watchOS 6.2 allows local users to execute kernel code. The IOHIDFamily component initializes memory incorrectly; Apple has not published the affected function, data structure, or input path. Exploitation requires a malicious application to run locally and grants kernel privileges, placing the affected device under application-controlled kernel code.
The record
- CVE
- CVE-2020-3919
- Published
- Apr 1, 2020
- Updated
- Aug 4, 2024
- Vendor
- Apple
- Product
- iOS
- Classifications
- CWE-665, T1068, T1404
- 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.
Weakness, pattern, technique
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