CVE-2010-0018 in the critical feed json
Integer overflow in the Embedded OpenType (EOT) Font Engine (t2embed.dll) in Microsoft Windows 2000 SP4; Windows XP SP2 and SP3; Windows Se…
published 16y ago modified 4mo ago also EUVD-2010-0050
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 26.5%
- EPSS 26.5% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known
Summary
Integer overflow in the Embedded OpenType (EOT) Font Engine (t2embed.dll) in Microsoft Windows 2000 SP4; Windows XP SP2 and SP3; Windows Server 2003 SP2; Windows Vista Gold, SP1, and SP2; Windows Server 2008 Gold, SP2, and R2; and Windows 7 allows remote attackers to execute arbitrary code via compressed data that represents a crafted EOT font, aka "Microtype Express Compressed Fonts Integer Flaw in the LZCOMP Decompressor Vulnerability."
Is CVE-2010-0018 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
26.52% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
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-189 Numeric Errors
References
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2010/ms10-001
vendor-advisory
-
secunia.com
/advisories/35457
third-party-advisory, vendor-advisory
-
vupen.com
/english/advisories/2010/0095
vdb-entry, vendor-advisory
- blogs.technet.com /srd/archive/2010/01/12/ms10-001-font-file-decompression-vulnerability.aspx
-
securitytracker.com
/id?1023432
vdb-entry
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A8324
vdb-entry, signature
-
us-cert.gov
/cas/techalerts/TA10-012B.html
third-party-advisory, us-government-resource
-
securityfocus.com
/bid/37671
vdb-entry
-
osvdb.org
/61651
vdb-entry
Sources
- CVE List CVE-2010-0018
- NVD CVE-2010-0018
Fencer Intel 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.