# CVE-2015-2464: Memory corruption in n/a

> Remote attackers can execute arbitrary code by tricking users into opening a crafted TrueType font in affected Microsoft products.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Aug 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-g64m-cw55-x3j7

## What is CVE-2015-2464?

CVE-2015-2464 is a critical memory corruption vulnerability in Microsoft .Net Framework, published on 15 Aug 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Microsoft Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT Gold and 8.1, Office 2007 SP3 and 2010 SP2, Live Meeting 2007 Console, Lync 2010, Lync 2010 Attendee, Lync 2013 SP1, Lync Basic 2013 SP1, Silverlight before 5.1.40728, and .NET Framework 3.0 SP2, 3.5, 3.5.1, 4, 4.5, 4.5.1, 4.5.2, and 4.6 allow remote attackers to execute arbitrary code via a crafted TrueType font, aka "TrueType Font Parsing Vulnerability," a different vulnerability than CVE-2015-2463.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 14 products.


Products: Microsoft .Net Framework, Microsoft Live Meeting, Microsoft Lync, Microsoft Lync Basic, Microsoft Office, Microsoft Silverlight, Microsoft Windows 7, Microsoft Windows 8, Microsoft Windows 8.1, Microsoft Windows Rt, Microsoft Windows Rt 8.1, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Vista.

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

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

## Is CVE-2015-2464 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-2464 exists.

Public exploit code:

- Microsoft Windows - 'win32k.sys' TTF Font Processing win32k!fsc_BLTHoriz Out-of-Bounds Pool Write (exploitdb)

## 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-2015-2464 and fix it if it is affected.

What it is: CVE-2015-2464 is a critical memory corruption vulnerability in Microsoft .Net Framework, published on 15 Aug 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-2464 exists.

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

## Sources

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

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