Bluetooth traffic disclosure via pairing-key extraction
Published Jan 12, 2024 · Updated Apr 2, 2026
Information disclosure in Apple Magic Keyboard Firmware before 2.0.6 allows physically proximate attackers to monitor Bluetooth traffic. Apple identifies faulty session management in the Bluetooth component but has not published the specific check that mishandles pairing state. Physical access to the accessory is required to extract its pairing key; the documented consequence is passive traffic monitoring, not modification or interruption.
Summary
What happened
Information disclosure in Apple Magic Keyboard Firmware before 2.0.6 allows physically proximate attackers to monitor Bluetooth traffic. Apple identifies faulty session management in the Bluetooth component but has not published the specific check that mishandles pairing state. Physical access to the accessory is required to extract its pairing key; the documented consequence is passive traffic monitoring, not modification or interruption.
The record
- CVE
- CVE-2024-0230
- Published
- Jan 12, 2024
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- Magic Keyboard Firmware
- Classifications
- T1040
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 12, 2024CVE publishedPublication date reported by the CVE source.
- Apr 2, 2026Record 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=0 <2.0.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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