Kernel-layout disclosure via Bluetooth out-of-bounds read
Published Jun 9, 2020 · Updated Aug 4, 2024
An out-of-bounds read in the Bluetooth component of Apple macOS before 10.15.5 allows local users to disclose kernel memory layout. The Bluetooth code reads beyond a buffer boundary because its bounds checking does not reject an out-of-range access; Apple has not named the function or input. Execution of a malicious local application and user interaction are required, and the reported consequence is limited to kernel-address layout disclosure.
Summary
What happened
An out-of-bounds read in the Bluetooth component of Apple macOS before 10.15.5 allows local users to disclose kernel memory layout. The Bluetooth code reads beyond a buffer boundary because its bounds checking does not reject an out-of-range access; Apple has not named the function or input. Execution of a malicious local application and user interaction are required, and the reported consequence is limited to kernel-address layout disclosure.
The record
- CVE
- CVE-2020-9831
- Published
- Jun 9, 2020
- Updated
- Aug 4, 2024
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-125
- Attack vector
- local
- Privileges
- Unavailable
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 <macOS Catalina 10.15.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.
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