← Back to results
Vulnerability record · public intelligence
CVE-2010-0232
HIGHCISA KEV

CVE-2010-0232

Published Jan 21, 2010 · Updated Oct 23, 2026

Severity · CVSSHIGH · 7.8
Known exploitationCISA KEV listed
EPSS / likelihood28.73%
QFinch risk score95 / 100

Original summary

Normalized public record · Updated Oct 23, 2026

The kernel in Microsoft Windows NT 3.1 through Windows 7, including Windows 2000 SP4, Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista Gold, SP1, and SP2, and Windows Server 2008 Gold and SP2, when access to 16-bit applications is enabled on a 32-bit x86 platform, does not properly validate certain BIOS calls, which allows local users to gain privileges by crafting a VDM_TIB data structure in the Thread Environment Block (TEB), and then calling the NtVdmControl function to start the Windows Virtual DOS Machine (aka NTVDM) subsystem, leading to improperly handled exceptions involv

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

The kernel in Microsoft Windows NT 3.1 through Windows 7, including Windows 2000 SP4, Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista Gold, SP1, and SP2, and Windows Server 2008 Gold and SP2, when access to 16-bit applications is enabled on a 32-bit x86 platform, does not properly validate certain BIOS calls, which allows local users to gain privileges by crafting a VDM_TIB data structure in the Thread Environment Block (TEB), and then calling the NtVdmControl function to start the Windows Virtual DOS Machine (aka NTVDM) subsystem, leading to improperly handled exceptions involving the #GP trap handler (nt!KiTrap0D), aka "Windows Kernel Exception Handler Vulnerability."

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

CVEKEVNVDEPSSEXPLOITDBMETASPLOIT
SSVC priority
IMMEDIATE
Confidence
95%
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. [dailydave] 20100119 We hold these axioms to be self evident ↗
  2. lock.cmpxchg8b.com ↗
  3. blogs.technet.com ↗
  4. MS10-015 ↗
  5. www.microsoft.com ↗
  6. TA10-040A ↗
  7. 1023471 ↗
  8. 20100119 Microsoft Windows NT #GP Trap Handler Allows Users to Switch Kernel Stack ↗
  9. ADV-2010-0179 ↗
  10. 37864 ↗
  11. 38265 ↗
  12. 20100119 Microsoft Windows NT #GP Trap Handler Allows Users to Switch Kernel Stack ↗

Record history

Published Jan 21, 2010 · Last refreshed Oct 23, 2026