Loading vulnerability…
Patriot Viper RGB before version 1.1 ships the kernel drivers MsIo64.sys and MsIo32.sys with insufficient access restrictions. According to the provided content, local users, including low-integrity processes, can use these drivers to map \Device\PhysicalMemory into their own process by invoking ZwOpenSection and ZwMapViewOfSection. This exposes arbitrary physical memory read and write capability from user mode through the driver, enabling direct manipulation of kernel-relevant memory and resulting in privilege escalation to NT AUTHORITY\SYSTEM.
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) local privilege escalation exploit for CVE-2019-18845, targeting the MsIo64.sys and MsIo32.sys drivers used by Patriot Viper RGB software prior to version 1.1 on Windows. The exploit is implemented in C and consists of a main source file (exploit.c) and a header (exploit.h). The code opens a handle to the vulnerable device (\\.\MsIo) and sends a specially crafted structure to the driver using DeviceIoControl with the IOCTL code 0x80102040. This triggers the vulnerability, allowing the attacker to read and write arbitrary physical memory, which can be used to escalate privileges to SYSTEM. The repository includes Visual Studio project files for building the exploit. No network endpoints are involved; the attack vector is purely local, requiring execution on a vulnerable Windows system with the affected driver loaded.
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.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.