Loading vulnerability…
CVE-2024-0230 describes a session management vulnerability in the Magic Keyboard firmware prior to version 2.0.6. The flaw allows an attacker with physical access to the keyboard to extract its Bluetooth pairing key, which could then be used to monitor Bluetooth traffic between the keyboard and paired devices. The vulnerability was addressed by improving session management checks in the firmware update.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a Bash script (poc.sh) that serves as a helper for demonstrating and exploiting CVE-2024-0230, a Bluetooth vulnerability. The script is designed to be run as root on a Linux system and automates the process of preparing the environment, ensuring required utilities and packages are installed, and managing Bluetooth device state. It clones an external repository ('hi_my_name_is_keyboard') containing the actual keystroke injection exploit script. The main logic scans for nearby Bluetooth devices, filters out excluded MAC addresses, and attempts to inject keystrokes into discovered devices using the external Python script. The script maintains lists of discovered, excluded, and already-attacked devices to avoid repeated attacks. The repository consists of a README.md with usage instructions and the main poc.sh script, which orchestrates the attack. The exploit targets Bluetooth devices vulnerable to CVE-2024-0230 and demonstrates the attack in a proof-of-concept manner.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.