Kernel-memory disclosure via improper state management
Published Jun 9, 2020 · Updated Aug 4, 2024
Information disclosure in the Apple kernel across iOS, macOS, tvOS, and watchOS allows local users to read kernel memory. Apple identifies improper state management in the kernel but does not disclose the affected function, state transition, or attacker-controlled input. Local execution is required, and successful exploitation exposes kernel memory without reported integrity or availability impact.
Summary
What happened
Information disclosure in the Apple kernel across iOS, macOS, tvOS, and watchOS allows local users to read kernel memory. Apple identifies improper state management in the kernel but does not disclose the affected function, state transition, or attacker-controlled input. Local execution is required, and successful exploitation exposes kernel memory without reported integrity or availability impact.
The record
- CVE
- CVE-2020-9811
- Published
- Jun 9, 2020
- Updated
- Aug 4, 2024
- Vendor
- Apple
- Product
- iOS
- Classifications
- T1533, T1005
- 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