# CVE-2015-1671: Microsoft Windows Remote Code Execution

> Remote attackers can execute arbitrary code via a crafted TrueType font in the Windows DirectWrite library used by various 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:** Yes, since 25 May 2022 (CISA KEV)
- **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:** 13 May 2015
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-gr4p-px5x-x8jm

## What is CVE-2015-1671?

CVE-2015-1671 is a high-severity memory corruption vulnerability in Microsoft .Net Framework, published on 13 May 2015. 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

The Windows DirectWrite library, as used in Microsoft .NET Framework 3.0 SP2, 3.5, 3.5.1, 4, 4.5, 4.5.1, and 4.5.2; Office 2007 SP3 and 2010 SP2; Live Meeting 2007 Console; Lync 2010; Lync 2010 Attendee; Lync 2013 SP1; Lync Basic 2013 SP1; Silverlight 5 before 5.1.40416.00; and Silverlight 5 Developer Runtime before 5.1.40416.00, allows remote attackers to execute arbitrary code via a crafted TrueType font, aka "TrueType Font Parsing Vulnerability."

## Which versions are affected by CVE-2015-1671?

It affects 4 products.


Products: Microsoft .Net Framework, Microsoft Live Meeting, Microsoft Lync, Microsoft Silverlight.

## How do I fix CVE-2015-1671?

No fix has been published for CVE-2015-1671 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 15 Jun 2022.

## Is CVE-2015-1671 being exploited?

Yes. Attackers have exploited CVE-2015-1671 in the wild since at least 25 May 2022.

## 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-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)
- [CVE-2014-4121](https://insights.sbomify.com/CVE-2014-4121/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-1671 and fix it if it is affected.

What it is: CVE-2015-1671 is a high-severity memory corruption vulnerability in Microsoft .Net Framework, published on 13 May 2015. 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: Yes. Attackers have exploited CVE-2015-1671 in the wild since at least 25 May 2022.

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-2015-1671/ (Markdown: https://insights.sbomify.com/CVE-2015-1671/index.md)
```

## Sources

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

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