Loading vulnerability…
A vulnerability in MODAPI.sys, a driver used by MSI Dragon Center 2.0.104.0, allows low-privileged users to access kernel memory by issuing a crafted IOCTL 0x9c406104 call. This IOCTL exposes the MmMapIoSpace functionality, enabling mapping of arbitrary physical memory into user space, which can be abused to escalate 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-2021-29337, a local privilege escalation vulnerability in the MODAPI.sys driver used by MSI Dragon Center (version 2.0.104.0) on Windows 10. The exploit is implemented in C (modapi_poc.c) and demonstrates how a low-privileged user can interact with the vulnerable driver via a specific IOCTL (0x9C406104) to map and read arbitrary physical memory. The code allocates input and output buffers, crafts the necessary parameters, and uses DeviceIoControl to communicate with the driver. If successful, the exploit outputs a memory dump from the specified physical address. The README provides context, affected product/version, and a high-level description of the vulnerability. The main fingerprintable endpoint is the device file \\.\WinRing0_1_2_0, and the IOCTL code 0x9C406104 is used to trigger the vulnerability. The exploit is a POC and does not include weaponized payloads, but demonstrates the core vulnerability and its exploitation path.
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.