Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-0230: An attacker with physical access to the accessory may be able to extract its Bluetooth pairing key and monitor Bluetooth traffic in Apple Magic Keyboard Firmware Update

0
Low
VulnerabilityCVE-2024-0230cvecve-2024-0230
Published: Fri Jan 12 2024 (01/12/2024, 23:10:45 UTC)
Source: CVE Database V5
Vendor/Project: Apple
Product: Magic Keyboard Firmware Update

Description

A session management issue was addressed with improved checks. This issue is fixed in Magic Keyboard Firmware Update 2.0.6. An attacker with physical access to the accessory may be able to extract its Bluetooth pairing key and monitor Bluetooth traffic.

AI-Powered Analysis

AILast updated: 11/04/2025, 19:33:01 UTC

Technical Analysis

CVE-2024-0230 is a vulnerability in the Apple Magic Keyboard firmware that stems from insufficient session management controls. Specifically, the flaw allows an attacker who gains physical access to the keyboard accessory to extract the Bluetooth pairing key stored within the device. This key is critical for establishing and maintaining a secure Bluetooth connection between the keyboard and its paired host device. By extracting this key, the attacker can potentially monitor Bluetooth traffic, which may include keystrokes or other sensitive data transmitted over the wireless connection. The vulnerability does not allow modification or disruption of data (no integrity or availability impact), nor does it permit remote exploitation, as physical access is a prerequisite. Apple released firmware update 2.0.6 to address this issue by implementing improved session management checks that prevent unauthorized key extraction. The CVSS v3.1 base score is 2.4, indicating low severity, primarily due to the requirement for physical access and the limited confidentiality impact. No known exploits have been reported in the wild, and the affected versions are unspecified but presumed to be all versions prior to 2.0.6. This vulnerability highlights the importance of securing physical access to peripheral devices and maintaining up-to-date firmware to protect Bluetooth communications.

Potential Impact

For European organizations, the impact of CVE-2024-0230 is generally low but not negligible. The primary risk is the potential exposure of Bluetooth traffic between the Magic Keyboard and its paired device, which could include sensitive input data such as passwords or confidential information. However, since exploitation requires physical access to the keyboard, the threat is mostly relevant in environments where devices are shared, left unattended, or physically accessible to unauthorized personnel. This could include open office spaces, public workstations, or environments with lax physical security controls. The confidentiality impact is limited to Bluetooth traffic monitoring; integrity and availability of systems are unaffected. Organizations handling sensitive data or operating in regulated sectors (e.g., finance, government, healthcare) should be particularly cautious. The vulnerability does not facilitate remote attacks, so network perimeter defenses are not directly relevant. Overall, the impact is constrained by the attacker's need for physical access and the limited scope of data exposure.

Mitigation Recommendations

To mitigate CVE-2024-0230, European organizations should take the following specific actions: 1) Ensure all Apple Magic Keyboards are updated to firmware version 2.0.6 or later, which contains the fix for this vulnerability. 2) Implement strict physical security controls to prevent unauthorized access to peripheral devices, including locking workstations and securing peripherals when not in use. 3) Conduct regular audits of peripheral devices to detect any signs of tampering or unauthorized access. 4) Educate employees about the risks of leaving devices unattended and the importance of reporting lost or stolen accessories immediately. 5) Consider using endpoint security solutions that can detect unusual Bluetooth activity or pairing attempts. 6) In high-security environments, evaluate the use of alternative input devices with stronger physical security or encrypted communication protocols. 7) Maintain an inventory of all Bluetooth peripherals to quickly identify and update vulnerable devices. These measures go beyond generic advice by focusing on physical security and firmware management specific to the affected product.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
apple
Date Reserved
2024-01-03T22:26:44.836Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 683f034b182aa0cae27e666e

Added to database: 6/3/2025, 2:14:35 PM

Last enriched: 11/4/2025, 7:33:01 PM

Last updated: 12/4/2025, 2:50:12 AM

Views: 44

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats