CVE-2006-0143 in the critical feed json
Microsoft Windows Graphics Rendering Engine (GRE) allows remote attackers to corrupt memory and cause a denial of service (crash) via a WMF…
published 2006-01-09 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-0151
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 31.3%
- EPSS 31.3% chance of exploitation in 30 days, percentile 98%
- public exploits
- 1
- Exploit-DB
Summary
Microsoft Windows Graphics Rendering Engine (GRE) allows remote attackers to corrupt memory and cause a denial of service (crash) via a WMF file containing (1) ExtCreateRegion or (2) ExtEscape function calls with arguments with inconsistent lengths.
Patch / fix
Timeline
- First public exploit (EDB-27051)
- Published
Exploit prediction
31.27% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-27051 Microsoft Windows - Graphics Rendering Engine Multiple Memory Corruption Vulnerabilities dos, 2006-01-09
- securityfocus.com http://www.securityfocus.com/bid/16167 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-399 Resource Management Errors
References
-
securitytracker.com
/id?1015453
vdb-entry, patch
-
securityfocus.com
/bid/16167
vdb-entry, exploit
-
vupen.com
/english/advisories/2006/0115
vdb-entry, vendor-advisory
- lostmon.blogspot.com /2007/08/windows-extended-file-attributes-buffer.html
-
exchange.xforce.ibmcloud.com
/vulnerabilities/24044
vdb-entry
- blogs.technet.com /msrc/archive/2006/01/09/417198.aspx
-
securityfocus.com
/archive/1/421258/100/0/threaded
mailing-list
-
securityfocus.com
/archive/1/421257/100/0/threaded
mailing-list
Sources
- CVE List CVE-2006-0143
- NVD CVE-2006-0143
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.