Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2010-4398: Driver Improper Interaction with Windows Kernel Vulnerability

Published Dec 3, 2010 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS8.7%95th percentile
CISA KEVYesAdded Mar 28, 2022
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2010-4398CWE-121

CVE-2010-4398 is a stack-based buffer overflow involving RtlQueryRegistryValues in the Microsoft Windows kernel subsystem. A crafted REG_BINARY registry value associated with the system-default end-user-defined-character font allows local users to elevate privileges and bypass User Account Control. Affected releases include Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista SP1 and SP2, Windows Server 2008 Gold, SP2 and R2, and Windows 7. The underlying unsafe registry-query pattern uses RTL_QUERY_REGISTRY_DIRECT without adequate type validation. An incomplete fix left related administrator-reachable driver code paths vulnerable on fully updated Windows 7 and Windows Server 2008 R2, enabling registry-backed kernel shellcode execution during boot.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation of the original vulnerability permits local privilege escalation to kernel-level access and bypass of User Account Control. Related code paths left vulnerable by the incomplete fix permit an attacker who already has administrator privileges to execute kernel shellcode during boot and establish registry-backed persistence. The administrator requirement for these residual paths is distinct from the original local-user privilege-escalation vulnerability.

Mitigation

If you can’t patch tonight, do this now.

Mitigations are limited because this is a local kernel privilege-escalation flaw. Restrict local logon and code-execution opportunities, enforce least privilege, and monitor for suspicious modification of registry values associated with the vulnerable path, especially crafted REG_BINARY data in sensitive keys such as SystemDefaultEUDCFont. UAC should not be relied upon as a defense because the vulnerability can bypass it. Application control, EDR telemetry on registry tampering and kernel exploit behavior, and rapid isolation of legacy hosts can reduce exploitation risk where patching is unavailable.

Remediation

Patch, then assume compromise.

Vulnerable registry-query call sites must validate registry value types before copying data into destination buffers. Microsoft introduced RTL_QUERY_REGISTRY_TYPECHECK for use with RTL_QUERY_REGISTRY_DIRECT to enforce this validation. The original fix did not comprehensively protect administrator-reachable code paths; fully updated Windows 7 and Windows Server 2008 R2 retained related vulnerabilities. A specific update that comprehensively resolves those residual paths is not identified.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows 7operating_system
Microsoft CorporationWindows Server 2003operating_system
Microsoft CorporationWindows Server 2008operating_system
Microsoft CorporationWindows Vistaoperating_system
Microsoft CorporationWindows Xpoperating_system
FAQ

Frequently asked questions

Is CVE-2010-4398 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Mar 28, 2022.
Is there a public exploit for CVE-2010-4398?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2010-4398.
Is there a patch for CVE-2010-4398?
Vulnerable registry-query call sites must validate registry value types before copying data into destination buffers. Microsoft introduced RTL_QUERY_REGISTRY_TYPECHECK for use with RTL_QUERY_REGISTRY_DIRECT to enforce this validation.
What products are affected by CVE-2010-4398?
Microsoft Corporation Windows 7, Microsoft Corporation Windows Server 2003, Microsoft Corporation Windows Server 2008, Microsoft Corporation Windows Vista, and Microsoft Corporation Windows Xp.
How severe is CVE-2010-4398?
CVE-2010-4398 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 8.7% (95th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+3 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence4Every report linking this CVE to a named adversary.
Associated malware6Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.