CVE-2020-12856 is a vulnerability in OpenTrace, as used in COVIDSafe (through v1.0.17), TraceTogether, ABTraceTogether, and other similar contact tracing applications on iOS and Android. The vulnerability arises from the way Bluetooth is used for proximity tracing, allowing remote attackers to perform long-term re-identification attacks. This undermines the intended privacy guarantees of the apps by enabling tracking of users over time.
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 proof-of-concept (PoC) exploit for CVE-2020-12856, a vulnerability in the Android version of the COVIDSafe contact tracing app (and similar apps) that allows an attacker to silently bond with a target device via Bluetooth. The exploit consists of Python scripts that set up a GATT server advertising a specific service UUID. When a vulnerable app connects and reads the characteristic, the device is bonded without user interaction, exposing permanent identifiers (Bluetooth address and IRK) that can be used for long-term tracking. The repository includes setup instructions (setup.sh), the main exploit script (exploit1.py), and supporting code for GATT advertisement and server functionality. The exploit targets Bluetooth Low Energy (BLE) and requires physical proximity to the target device. No network endpoints are involved; the attack is performed over Bluetooth. The code is well-structured and serves as a practical demonstration of the vulnerability.
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.