# CVE-2006-5270: Integer overflow in n/a

> Integer overflow in Microsoft Malware Protection Engine allows remote code execution via crafted PDF files, requiring user interaction.

- **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 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-w9r9-5xpf-rvjr

## What is CVE-2006-5270?

CVE-2006-5270 is a critical vulnerability in n/a, published on 13 Feb 2007. 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 the Microsoft Malware Protection Engine (mpengine.dll), as used by Windows Live OneCare, Antigen, Defender, and Forefront Security, allows user-assisted remote attackers to execute arbitrary code via a crafted PDF file.

## Which versions are affected by CVE-2006-5270?

It affects 5 products.


Products: Microsoft Antigen, Microsoft Forefront Security, Microsoft Malware Protection Engine, Microsoft Windows Defender, Microsoft Windows Live Onecare.

## How do I fix CVE-2006-5270?

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

## Is CVE-2006-5270 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-5270 and fix it if it is affected.

What it is: CVE-2006-5270 is a critical vulnerability in n/a, published on 13 Feb 2007. 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-2006-5270 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-2006-5270/ (Markdown: https://insights.sbomify.com/CVE-2006-5270/index.md)
```

## Sources

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

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