CVE-2018-8410 is an elevation of privilege vulnerability in the Windows Kernel API, where improper handling of registry objects in memory allows a local attacker to gain elevated privileges. The vulnerability affects multiple versions of Windows, including Windows 7, 8.1, 10, and various Windows Server editions.
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 (1 hidden).
This repository contains a proof-of-concept (PoC) exploit for CVE-2018-8410, a Windows Kernel Registry Elevation of Privilege vulnerability. The main file, 'poc.cpp', is a C++ program that demonstrates the vulnerability by opening a specific registry key (\REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\009) and calling low-level Windows Native API functions (NtOpenKey and NtEnumerateKey). The exploit triggers a double dereference in the Windows kernel, which can result in a system crash (BSOD) or potentially allow privilege escalation. The exploit requires local execution on a vulnerable Windows system. The repository is minimal, containing only a README and the PoC source code.
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.