# CVE-2011-0976: Memory corruption in n/a

> Remote attackers can execute arbitrary code or cause denial of service via a malicious PowerPoint document exploiting memory corruption in Office Art containers.

- **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:** 10 Feb 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-32pv-j8mv-f3hg

## What is CVE-2011-0976?

CVE-2011-0976 is a critical memory corruption vulnerability in Microsoft Powerpoint, published on 10 Feb 2011. 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 2002 SP3, 2003 SP3, and 2007 SP2; Office 2004 and 2008 for Mac; Open XML File Format Converter for Mac; Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats SP2; and PowerPoint Viewer 2007 SP2 do not properly handle Office Art containers that have invalid records, which allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a PowerPoint document with a container that triggers certain access to an uninitialized object, aka "OfficeArt Atom RCE Vulnerability."

Weakness: CWE-264

## Which versions are affected by CVE-2011-0976?

It affects 1 product.


Products: Microsoft Powerpoint.

## How do I fix CVE-2011-0976?

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

## Is CVE-2011-0976 being exploited?

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

## Other vulnerabilities in Microsoft Powerpoint

- [CVE-2010-2572](https://insights.sbomify.com/CVE-2010-2572/): Microsoft PowerPoint Buffer Overflow (high 7.8, exploited in the wild)
- [CVE-2011-3396](https://insights.sbomify.com/CVE-2011-3396/): Path traversal in n/a (critical 9.3)
- [CVE-2011-1270](https://insights.sbomify.com/CVE-2011-1270/): Memory corruption in n/a (critical 9.3)
- [CVE-2010-3141](https://insights.sbomify.com/CVE-2010-3141/): Path traversal in n/a (critical 9.3)
- [CVE-2010-3142](https://insights.sbomify.com/CVE-2010-3142/): Path traversal in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-0976 and fix it if it is affected.

What it is: CVE-2011-0976 is a critical memory corruption vulnerability in Microsoft Powerpoint, published on 10 Feb 2011. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2011-0976 in the wild and no public exploit code.

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

## Sources

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

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