# CVE-2015-2424: Microsoft PowerPoint Memory Corruption

> Remote attackers can execute arbitrary code or cause denial of service via crafted Office documents in Microsoft Word and PowerPoint.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Mar 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Jul 2015
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-rvvj-j63r-j9x4

## What is CVE-2015-2424?

CVE-2015-2424 is a high-severity memory corruption vulnerability in Microsoft Excel Viewer, published on 14 Jul 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 PowerPoint 2007 SP3, Word 2007 SP3, PowerPoint 2010 SP2, Word 2010 SP2, PowerPoint 2013 SP1, Word 2013 SP1, and PowerPoint 2013 RT SP1 allow remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted Office document, aka "Microsoft Office Memory Corruption Vulnerability."

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 6 products.


Products: Microsoft Excel Viewer, Microsoft Office, Microsoft Office Compatibility Pack, Microsoft Powerpoint, Microsoft Word, Microsoft Word Viewer.

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

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

## Is CVE-2015-2424 being exploited?

Yes. Attackers have exploited CVE-2015-2424 in the wild since at least 3 Mar 2022.

## Other vulnerabilities in Microsoft Excel Viewer

- [CVE-2019-0541](https://insights.sbomify.com/CVE-2019-0541/): Microsoft MSHTML Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2013-3906](https://insights.sbomify.com/CVE-2013-3906/): Microsoft Graphics Component Memory Corruption (high 7.8, exploited in the wild)
- [CVE-2008-0113](https://insights.sbomify.com/CVE-2008-0113/): Memory corruption in n/a (critical 9.3)
- [CVE-2018-8432](https://insights.sbomify.com/CVE-2018-8432/): Memory corruption in Microsoft Excel Viewer (high 7.8)
- [CVE-2019-0540](https://insights.sbomify.com/CVE-2019-0540/): Security feature bypass in Microsoft Excel Viewer (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-2424 is a high-severity memory corruption vulnerability in Microsoft Excel Viewer, published on 14 Jul 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: Yes. Attackers have exploited CVE-2015-2424 in the wild since at least 3 Mar 2022.

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

## Sources

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

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