CVE-2009-0081 in the critical feed json
The graphics device interface (GDI) implementation in the kernel in Microsoft Windows 2000 SP4, XP SP2 and SP3, Server 2003 SP1 and SP2, Vi…
published 2009-03-10 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-0090
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 32.1%
- EPSS 32.1% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known
Summary
The graphics device interface (GDI) implementation in the kernel in Microsoft Windows 2000 SP4, XP SP2 and SP3, Server 2003 SP1 and SP2, Vista Gold and SP1, and Server 2008 does not properly validate input received from user mode, which allows remote attackers to execute arbitrary code via a crafted (1) Windows Metafile (aka WMF) or (2) Enhanced Metafile (aka EMF) image file, aka "Windows Kernel Input Validation Vulnerability."
Exploit prediction
32.11% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2009/ms09-006
vendor-advisory
-
securitytracker.com
/id?1021826
vdb-entry
-
us-cert.gov
/cas/techalerts/TA09-069A.html
third-party-advisory, us-government-resource
-
osvdb.org
/52522
vdb-entry
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A6202
vdb-entry, signature
-
secunia.com
/advisories/34117
third-party-advisory
-
vupen.com
/english/advisories/2009/0659
vdb-entry
- support.avaya.com /elmodocs2/security/ASA-2009-079.htm
- support.nortel.com /go/main.jsp?cscat=BLTNDETAIL&DocumentOID=842987&poid=
-
securityfocus.com
/bid/34012
vdb-entry
Sources
- CVE List CVE-2009-0081
- NVD CVE-2009-0081
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.