Remote code execution via CoreBluetooth memory corruption
Published Apr 1, 2020 · Updated Aug 4, 2024
Memory corruption in CoreBluetooth in Apple macOS before Catalina 10.15.3 allows remote attackers to crash applications or execute code. CoreBluetooth processes untrusted input without sufficient validation, corrupting memory; Apple has not disclosed the specific parser, field, or memory operation. No authentication or user interaction is required, and successful processing can terminate the affected application or run attacker-controlled code.
Summary
What happened
Memory corruption in CoreBluetooth in Apple macOS before Catalina 10.15.3 allows remote attackers to crash applications or execute code. CoreBluetooth processes untrusted input without sufficient validation, corrupting memory; Apple has not disclosed the specific parser, field, or memory operation. No authentication or user interaction is required, and successful processing can terminate the affected application or run attacker-controlled code.
The record
- CVE
- CVE-2020-3850
- Published
- Apr 1, 2020
- Updated
- Aug 4, 2024
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-20, CWE-787, T1203
- Attack vector
- network
- 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 <macOS Catalina 10.15.3
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