dbcve.org
.net FrameworkApplication · Microsoft

CVE-2013-3129

HIGH · 7.8 CVSS v3.1 Published 2013-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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
Microsoft .NET Framework 3.0 SP2, 3.5, 3.5.1, 4, and 4.5; Silverlight 5 before 5.1.20513.0; win32k.sys in the kernel-mode drivers, and GDI+, DirectWrite, and Journal, in Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows Server 2012, and Windows RT; GDI+ in Office 2003 SP3, 2007 SP3, and 2010 SP1; GDI+ in Visual Studio .NET 2003 SP1; and GDI+ in Lync 2010, 2010 Attendee, 2013, and Basic 2013 allow remote attackers to execute arbitrary code via a crafted TrueType Font (TTF) file, aka "TrueType Font Parsing Vulnerability."

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 · high confidence

This is a memory corruption vulnerability in TrueType Font (TTF) parsing logic affecting multiple Microsoft components including GDI+, DirectWrite, win32k.sys, .NET Framework, Silverlight, and related products. Attackers can achieve remote code execution by tricking users into opening specially crafted TTF files, which the vulnerable font parsing code processes without proper bounds checking.

MitigationApply Microsoft security updates (MS13-052 and related bulletins) to all affected products. Until patches are applied, exercise extreme caution with TTF files from untrusted sources and consider disabling font file preview handlers in email clients.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
.net FrameworkApplication
Affected:= 3.0= 3.5= 3.5.1= 4.0= 4.5
LyncApplication
Affected:= 2010= 2013
Lync BasicApplication
Affected:= 2013
OfficeApplication
Affected:= 2003= 2007= 2010
SilverlightApplication
Affected:= 5.0.60401.0= 5.0.60818.0= 5.0.61118.0= 5.1.10411.0= 5.1.20125.0
Visual Studio .netApplication
Affected:= 2003
Windows 7Operating system
Affected:all versions
Windows 8Operating 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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check .NET Framework version
    Open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.0, v3.5, v4\Full. Check the Release value and compare against known version numbers for your installation.
    Affected if The installed .NET Framework version is 3.0, 3.5, 3.5.1, 4.0, or 4.5
  2. Check Silverlight version
    Open Control Panel > Programs and Features, or navigate to C:\Program Files\Microsoft Silverlight and check the version info, or run 'slmgr.vbs /dli' from command prompt.
    Affected if The installed Silverlight version is 5.0.60401.0, 5.0.60818.0, 5.0.61118.0, 5.1.10411.0, or 5.1.20125.0
  3. Check Microsoft Office version
    Open any Office application, go to File > Account > About [App], or open registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration for Office 2013+.
    Affected if The installed Microsoft Office version is 2003, 2007, or 2010
  4. Check Microsoft Lync version
    Open Lync, go to Help > About Microsoft Lync, or check registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Lync entry.
    Affected if The installed Lync version is 2010 or 2013
  5. Check Windows version
    Run 'winver' from Start menu search, or right-click This PC > Properties, or run 'systeminfo' from command prompt.
    Affected if The operating system is Windows 7 or Windows 8 (any version)

You are affected if any vulnerable Microsoft component (.NET Framework, Silverlight, Office, Lync, or Windows 7/8) is installed and the system can process TTF font files, which is a standard font rendering capability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Microsoft security updates (MS13-052 and related bulletins) to all affected products. Until patches are applied, exercise extreme caution with TTF files from untrusted sources and consider disabling font file preview handlers in email clients.

Fix this in .net Framework Scoped from the published advisory
  • Consultation8.0 h
  • Implementation40.0 h
  • Testing24.0 h
  • Review / QA8.0 h
80.0 hours of engineering $13,840
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $22,144.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-3129 — 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-2013-3129 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