# CVE-2008-0120: Integer overflow in n/a

> Remote attackers can execute arbitrary code by tricking users into opening a malicious PowerPoint file in PowerPoint Viewer 2003.

- **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:** 13 Aug 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-82v2-59rq-5h73

## What is CVE-2008-0120?

CVE-2008-0120 is a critical vulnerability in n/a, published on 13 Aug 2008. 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

Integer overflow in Microsoft PowerPoint Viewer 2003 allows remote attackers to execute arbitrary code via a PowerPoint file with a malformed picture index that triggers memory corruption, related to handling of CString objects, aka "Memory Allocation Vulnerability."

Weakness: CWE-399

## Which versions are affected by CVE-2008-0120?

It affects 1 product.


Products: Microsoft Office Powerpoint Viewer.

## How do I fix CVE-2008-0120?

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

## Is CVE-2008-0120 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-0121](https://insights.sbomify.com/CVE-2008-0121/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-0120 and fix it if it is affected.

What it is: CVE-2008-0120 is a critical vulnerability in n/a, published on 13 Aug 2008. 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-2008-0120 in the wild and no public exploit code.

Affected product: n/a. 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-2008-0120/ (Markdown: https://insights.sbomify.com/CVE-2008-0120/index.md)
```

## Sources

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

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