Loading vulnerability…
Shanda MapleStory Online V160 contains an integer signedness error in a kernel driver’s handling of IOCTL 0x8000c01c input. The driver does not validate the supplied input value, allowing an integer signedness condition to cause a heap-based buffer underflow and enabling local 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 local privilege escalation exploit targeting the SdoKeyCrypt.sys driver, which is installed by the Chinese version of MapleStory Online (by Shanda Group). The exploit (poc.cpp) is a C++ proof-of-concept that interacts with the vulnerable driver via DeviceIoControl calls to trigger a heap underflow in the driver's IOCTL handler. By exploiting this vulnerability, the code disables SMEP and executes shellcode in kernel mode, ultimately spawning a SYSTEM-level shell (cmd.exe). The exploit is effective on Windows 10 versions 1709 and 1803, but not on 1809 and later due to mitigations. The repository consists of a detailed README.md explaining the vulnerability, exploitation steps, and usage instructions, and a single C++ exploit file (poc.cpp). Key fingerprintable endpoints include the device name (\\.\SdoKeyCrypt), the driver file path (C:\Windows\System32\SdoKeyCrypt.sys), and the launched shell (cmd.exe).
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.