dbcve.org
Windows 2000Operating system · Microsoft

CVE-2006-0010

HIGH · 9.3 CVSS v2.0 Published 2006-01-10
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Heap-based buffer overflow in T2EMBED.DLL in Microsoft Windows 2000 SP4, XP SP1 and SP2, and Server 2003 up to SP1, Windows 98, and Windows ME allows remote attackers to execute arbitrary code via an e-mail message or web page with a crafted Embedded Open Type (EOT) web font that triggers the overflow during decompression.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-119

The program reads or writes outside the bounds of an allocated buffer, corrupting adjacent memory. With crafted input an attacker can overwrite control data and, with effort, redirect execution to their own code. Remediation ranges from bounds checking and safe library functions to compiler mitigations, usually alongside a careful audit of the surrounding code.

General guidance for the memory buffer bounds error class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 2000Operating system
Affected:all versions
Windows 2003 ServerOperating system
Affected:= datacenter_64-bit= enterprise= enterprise_64-bit= r2= standard= standard_64-bit= web
Windows 98Operating system
Affected:all versions
Windows 98seOperating system
Affected:all versions
Windows MeOperating system
Affected:all versions
Windows NtOperating system
Affected:= 3.5.1= 4.0
Windows XpOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch secunia.com →
Recommended fix High confidence

For end-of-life systems (Windows 98, Windows 98SE, Windows ME, Windows NT 4.0), upgrade to a supported Windows version such as Windows XP with Service Pack 3 or later, or Windows Server 2003 with current service packs. For Windows 2000, Windows XP, and Windows Server 2003, ensure installation of all

  1. Identify the exact Windows version and Service Pack level from the affected system using 'winver' or 'systeminfo'
  2. Locate and apply Microsoft Security Bulletin MS06-002, which addresses the T2EMBED.DLL vulnerability. This bulletin was released January 10, 2006.
  3. Download the appropriate patch for the specific Windows version from Microsoft's official Security Bulletin MS06-002: https://docs.microsoft.com/en-us/security-updates/securitybulletins/2006/ms06-002
  4. Apply the patch and restart the system as directed
  5. Verify the patch was successfully installed by checking for the presence of updated T2EMBED.DLL version or by confirming the security update appears in 'Add or Remove Programs' under 'Show Updates'
Caveat Risk is minimal for applying this specific patch; however, ensure backup of critical data before applying any system updates. Note that Windows 98/98SE/ME/NT are end-of-life and no longer receive official Microsoft security patches.

Generated from the published advisory — verify against the referenced sources before acting.

We can apply and verify the patch for your build — typical engagement from $3,200. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-0010 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2006-0010 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data