# CVE-2013-3129: Code injection in n/a

> Remote attackers can execute arbitrary code by tricking users into opening a crafted TrueType Font file in affected Windows and Microsoft applications.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Jul 2013
- **Updated:** 16 Jan 2025
- **Also known as:** GHSA-rgv9-4g5g-3mp2

## What is CVE-2013-3129?

CVE-2013-3129 is a high-severity code injection vulnerability in Microsoft .Net Framework, published on 10 Jul 2013. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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."

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2013-3129?

It affects 14 products.


Products: Microsoft .Net Framework, Microsoft Lync, Microsoft Lync Basic, Microsoft Office, Microsoft Silverlight, Microsoft Visual Studio .Net, Microsoft Windows 7, Microsoft Windows 8, Microsoft Windows Rt, Microsoft Windows Server 2003, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Vista, Microsoft Windows Xp.

## How do I fix CVE-2013-3129?

No fix has been published for CVE-2013-3129 yet. Limit exposure of the affected software until one is available.

## Is CVE-2013-3129 being exploited?

There is no known exploitation of CVE-2013-3129 in the wild and no public exploit code.

## Other vulnerabilities in Microsoft .Net Framework

- [CVE-2020-0646](https://insights.sbomify.com/CVE-2020-0646/): Microsoft .NET Framework Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2017-8759](https://insights.sbomify.com/CVE-2017-8759/): Microsoft .NET Framework Remote Code Execution (high 7.8, exploited in the wild)
- [CVE-2015-1671](https://insights.sbomify.com/CVE-2015-1671/): Microsoft Windows Remote Code Execution (high 7.8, exploited in the wild)
- [CVE-2024-29059](https://insights.sbomify.com/CVE-2024-29059/): Microsoft .NET Framework Information Disclosure (high 7.5, exploited in the wild)
- [CVE-2014-4073](https://insights.sbomify.com/CVE-2014-4073/): Privilege escalation in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-3129 and fix it if it is affected.

What it is: CVE-2013-3129 is a high-severity code injection vulnerability in Microsoft .Net Framework, published on 10 Jul 2013. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2013-3129 in the wild and no public exploit code.

Affected product: Microsoft .Net Framework. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-3129/ (Markdown: https://insights.sbomify.com/CVE-2013-3129/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-3129
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-3129
- OSV: https://osv.dev/vulnerability/CVE-2013-3129

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-3129/
Summaries are generated and may contain mistakes; the official description above is the record.