Kernel code execution via insufficient input validation
Published Feb 27, 2020 · Updated Aug 4, 2024
Memory corruption in the Apple kernel before iOS 13.3.1 and watchOS 6.1.2 allows local users to execute code with kernel privileges. The kernel insufficiently validates application-controlled input before memory handling, but Apple has not disclosed the exact field, function, or corrupting operation. Exploitation requires an application already running on the device and grants kernel-level code execution.
Summary
What happened
Memory corruption in the Apple kernel before iOS 13.3.1 and watchOS 6.1.2 allows local users to execute code with kernel privileges. The kernel insufficiently validates application-controlled input before memory handling, but Apple has not disclosed the exact field, function, or corrupting operation. Exploitation requires an application already running on the device and grants kernel-level code execution.
The record
- CVE
- CVE-2020-3860
- Published
- Feb 27, 2020
- Updated
- Aug 4, 2024
- Vendor
- Apple
- Product
- iOS
- Classifications
- CWE-787, CWE-20, T1404
- Attack vector
- local
- Privileges
- authenticated
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 <iOS 13.3.1 and iPadOS 13.3.1
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