CVE-2010-0232
CVE-2010-0232 is a security flaw in Microsoft Windows, Microsoft’s operating system for PCs and servers. Attackers can crash Microsoft Windows or stop it working. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 3 Mar 2022.[1]
Microsoft Windows is in things households have, such as phones, computers, browsers and everyday apps, so the fix matters at home as much as at work. Microsoft has published a fix or advice.
Description
CISA calls it a kernel exception handler in Microsoft Windows. In its words: “The kernel in Microsoft Windows, 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.”[1]
The CVE record adds: “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."”[2]
The underlying weakness is permissions and access control (CWE-264), in MITRE’s list of common software weaknesses.
It scores 7.8 out of 10 on the Common Vulnerability Scoring System, which rates it high, scored by NVD using CVSS 3.1.[2]
Affected versions
NVD’s record doesn’t list version ranges for it; Microsoft’s advisory has them[3]. CISA names the product as Microsoft Windows.
Every device with Microsoft Windows needs the update.
Exploitation
CISA added it to its catalog of known exploited vulnerabilities on 3 Mar 2022, 4,424 days after it was made public. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 24 Mar 2022 to fix it.[1]
FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at 29%. That’s in the top 2% of the flaws it scores.[4]
CISA assesses it as not automatable: each attack takes some work.
CISA doesn’t say who was attacked, or how.
Fix
Microsoft has published a fix or advice.[3] CISA’s required action: “Apply updates per vendor instructions.”[1]
- Update Microsoft Windows now.On Windows: Settings, Windows Update, Check for updates, then restart. Office updates come the same way, or from any Office app: File, Account, Update Options. Then turn on automatic updates, so the next fix arrives on its own.
- If there’s no update, stop using it.CISA’s advice when a flaw being used in attacks has no fix is to stop using the product until it does.
Timeline
| Date | Event |
|---|---|
| The flaw is made public in the National Vulnerability Database, with a severity score of 7.8.[2] | |
| CISA adds it to its catalog of flaws known to be used in attacks.[1] | |
| CISA’s deadline for US government agencies to fix it.[1] | |
| FIRST puts the odds of it being used in attacks in the next 30 days at 29%.[4] |
See also
Other Microsoft Windows flaws
- CVE-2026-96951: command injection ·
- CVE-2026-85880: heap-based buffer overflow ·
- CVE-2026-81963: link following ·
- CVE-2008-4250: buffer overflow ·
- CVE-2026-32202: protection mechanism failure ·
- CVE-2025-60710: link following ·
Other permissions and access control flaws
- CVE-2015-3246, Red Hat Libuser: race condition ·
- CVE-2013-0643, Adobe Flash Player: incorrect default permissions ·
- CVE-2015-0310, Adobe Flash Player: ASLR bypass ·
- CVE-2013-3993, IBM InfoSphere BigInsights: invalid input ·
- CVE-2013-0422, Oracle Java Runtime Environment (JRE): JRE remote code execution ·
Added the same day
- CVE-2022-20708, Cisco Small Business RV160, RV260, RV340, and RV345 Series Routers: small business RV series routers stack-based buffer overflow ·
- CVE-2022-20703, Cisco Small Business RV160, RV260, RV340, and RV345 Series Routers: small business RV series routers stack-based buffer overflow ·
- CVE-2022-20701, Cisco Small Business RV160, RV260, RV340, and RV345 Series Routers: small business RV series routers stack-based buffer overflow ·
- CVE-2022-20700, Cisco Small Business RV160, RV260, RV340, and RV345 Series Routers: small business RV series routers stack-based buffer overflow ·
- CVE-2022-20699, Cisco Small Business RV160, RV260, RV340, and RV345 Series Routers: small business RV series routers stack-based buffer overflow ·
Every Microsoft flaw on CISA’s list · Everything added in March 2022
References
- ^ Cybersecurity and Infrastructure Security Agency. “Microsoft Windows Kernel Exception Handler Vulnerability”. Known Exploited Vulnerabilities Catalog, added 3 Mar 2022.
- ^ National Institute of Standards and Technology. “CVE-2010-0232 Detail”. National Vulnerability Database, published 21 Jan 2010.
- ^ Microsoft. Advisories and fixes: docs.microsoft.com.
- ^ FIRST. “Exploit Prediction Scoring System”. EPSS 0.287, percentile 98.1, 31 Oct 2026.
- CVE Program. “CVE-2010-0232”. The official CVE record.
This article is built from CISA’s catalog (version 2026.10.30), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.