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

> Remote attackers can execute arbitrary code via a crafted OpenType font due to a buffer overflow in the Adobe Type Manager Library.

- **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:** 9 Sep 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-qcc8-wpcw-q7r5

## What is CVE-2015-2510?

CVE-2015-2510 is a critical memory corruption vulnerability in Microsoft Office, published on 9 Sep 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

Buffer overflow in the Adobe Type Manager Library in Microsoft Windows Vista SP2, Windows Server 2008 SP2, Office 2007 SP3, Office 2010 SP2, Lync 2010, Lync 2010 Attendee, Lync 2013 SP1, Lync Basic 2013 SP1, and Live Meeting 2007 Console allows remote attackers to execute arbitrary code via a crafted OpenType font, aka "Graphics Component Buffer Overflow Vulnerability."

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 5 products.


Products: Microsoft Live Meeting Console, Microsoft Lync, Microsoft Office, Microsoft Windows Server 2008, Microsoft Windows Vista.

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

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

## Is CVE-2015-2510 being exploited?

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

Public exploit code:

- Microsoft Office 2007 - 'OGL.dll' ValidateBitmapInfo Bounds Check Failure (MS15-097) (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-2510 is a critical memory corruption vulnerability in Microsoft Office, published on 9 Sep 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-2510 exists.

Affected product: Microsoft Office. 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-2510/ (Markdown: https://insights.sbomify.com/CVE-2015-2510/index.md)
```

## Sources

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

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