Loading vulnerability…
CVE-2017-13672 is a vulnerability in QEMU's VGA display emulator. When QEMU is built with VGA display support, a local privileged user in the guest OS can trigger an out-of-bounds read during display update operations, leading to a crash of the QEMU process.
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-2017-13672, an out-of-bounds read vulnerability in the Cirrus VGA device emulation in QEMU. The exploit is implemented as a Linux kernel module (CVE-2017-13672.c) that directly manipulates VGA controller registers via I/O port access, aiming to trigger the vulnerable code path in QEMU's emulation layer. The Makefile is used to build the kernel module, and the pwn.sh script automates the process of building, loading, and unloading the module. The README clarifies that the exploit is intended to demonstrate a denial-of-service (DoS) condition. The exploit requires local access to a Linux system running a QEMU VM with the vulnerable Cirrus VGA device. No network endpoints are involved; the attack vector is local, requiring the ability to load kernel modules. The repository is structured with clear separation between source code, build scripts, and documentation, and is intended for research and demonstration purposes.
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.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.