Loading vulnerability…
A vulnerability exists in the bencoding parser of BitTorrent uTorrent through version 3.5.5 (build 45505), where the parser incorrectly handles nested bencoded dictionaries. This flaw can be exploited by a remote attacker to trigger a denial of service condition in the application.
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 proof-of-concept exploit for CVE-2020-8437, a vulnerability in uTorrent. The repository consists of a README describing the exploit, a LICENSE file, and a single payload file named 'malicious.torrent'. The payload is a specially crafted .torrent file with repeated 'ad' keys in its bencoded structure, designed to trigger the vulnerability when opened or processed by a vulnerable version of uTorrent. There is no executable code or script; the exploit is delivered entirely via the malicious torrent file. The attack vector is local, requiring the target to open the file. No network endpoints or remote services are involved. The repository is a minimal, file-based proof-of-concept for demonstrating 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.