Loading vulnerability…
CVE-2020-14364 is an out-of-bounds read/write vulnerability in the USB emulator component of QEMU prior to version 5.2.0. The flaw exists in the handling of USB packets from a guest, specifically when the USBDevice 'setup_len' exceeds the allocated 'data_buf[4096]' in the do_token_in and do_token_out routines. This can be triggered by a malicious guest, leading to memory corruption in the QEMU process on the host.
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 (PoC) exploit for CVE-2020-14364, a vulnerability in QEMU's USB emulation that allows for memory leakage from the host process. The repository consists of two files: a minimal README and the main exploit code (exp.c). The exploit is written in C and is intended to be run on a Linux system with access to a vulnerable QEMU/KVM virtual machine. The code interacts directly with the emulated USB controller via MMIO and DMA, using privileged instructions and direct memory access to manipulate the device state. It leaks the base address of the QEMU process and the address of the system() function, which can be used for further exploitation. The exploit requires root or equivalent privileges to access the necessary device files and execute privileged instructions. No network endpoints are present; the attack vector is local, targeting the virtualized hardware interface exposed by QEMU.
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.