CVE-2024-40893 is an authenticated operating system command injection vulnerability in Firewalla Box Software versions prior to 1.979. An attacker with authenticated access to the Bluetooth Low-Energy (BTLE) interface can exploit the network configuration service to inject arbitrary OS commands into parameters such as networkConfig.Interface.Phy.Eth0.Extra.PingTestIP, networkConfig.Interface.Phy.Eth0.Extra.DNSTestDomain, and networkConfig.Interface.Phy.Eth0.Gateway6. The vulnerability is exacerbated by the fact that configuration changes can be synced to the Firewalla cloud, allowing persistence even after hardware resets or firmware re-flashes. The BTLE authentication mechanism is weak, relying on a license UUID transmitted in plaintext and not user-changeable, making it susceptible to sniffing or brute force attacks.
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 is a Go-based proof-of-concept exploit for Firewalla devices, targeting Bluetooth Low Energy (BLE) vulnerabilities CVE-2024-40892 and CVE-2024-40893. The exploit operates in several stages: 1. It scans for Firewalla devices in BLE proximity and leaks the checksum of the device's License UUID. 2. If the full License UUID is obtained (either by brute-force or other means), the tool can back up the device configuration locally. 3. With the License UUID, it can provision root SSH credentials on the device (CVE-2024-40892). 4. It exploits three command injection vulnerabilities (CVE-2024-40893) by writing payloads to specific configuration fields, resulting in the creation of files on the device (e.g., /tmp/pwn5, /tmp/pwn6, /tmp/pwn7) as a demonstration of code execution. The code is organized into a main entry point (main.go) and supporting packages for BLE interaction (pkg/btapi) and cryptographic operations (pkg/fwsecurity). The exploit requires the attacker to be within BLE range of the target device and, for full exploitation, to know or recover the device's License UUID. The repository is operational and demonstrates real-world exploitation of the referenced CVEs, including credential provisioning and command execution on the target device.
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.