Loading vulnerability…
CVE-2019-13143 describes an HTTP parameter pollution vulnerability in the Shenzhen Dragon Brothers Fingerprint Bluetooth Round Padlock FB50 version 2.3. The vulnerability allows an attacker, with knowledge of the user ID, user name, and the lock's MAC address, to unbind the legitimate owner and bind the lock to their own account. These parameters are easily retrievable from the mobile application APIs, making exploitation trivial. The attacker can thus take complete control of the lock, denying access to the original owner.
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 contains a Python exploit script (pwnfb50.py) targeting the OKLOK FB50 smart lock, specifically exploiting CVE-2019-13143. The exploit abuses insecure API endpoints of the OKLOK cloud service to transfer ownership of any FB50 smart lock to an attacker. By providing their own user ID and the MAC address of the target lock, an attacker can use the script to query device information, retrieve the legitimate user's ID, unbind the legitimate user, and then bind their own user ID to the lock. The script interacts with several fingerprintable HTTPS endpoints on the oklok.com.cn domain. The repository also includes a brief README with usage instructions and a standard MIT license. The exploit is operational and demonstrates a real-world attack scenario against vulnerable smart locks.
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.