Loading vulnerability…
CVE-2020-13519 is a privilege escalation vulnerability in the WinRing0x64 driver used by NZXT CAM 4.8.0. The vulnerability exists in the handling of IRP 0x9c402088, where a specially crafted I/O request packet can be sent to the driver, resulting in increased privileges for the attacker. The flaw is due to insufficient validation of user-supplied input in the IRP handler, allowing unprivileged users to execute code with elevated privileges.
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-13519, targeting the WinRing0 driver on Windows systems. The repository consists of a README.md describing the intent and a single C source file (dos.c) implementing the exploit logic. The exploit opens a handle to the WinRing0 device (\\.\WinRing0_1_2_0), constructs a structure to write to a Model-Specific Register (MSR), and issues a DeviceIoControl call to the driver with a crafted IOCTL. The payload writes a value (0xffffffffffffffff) to the LSTAR MSR, which can cause a system crash (BSOD) or potentially be leveraged for privilege escalation. The exploit is local and requires access to the vulnerable driver. The code is a POC and is not fully weaponized or automated, as indicated by the README and the interactive prompt before triggering the exploit.
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.