# CVE-2010-0816: Integer overflow in n/a

> Remote attackers can execute arbitrary code via crafted POP3 or IMAP responses, requiring user interaction to receive email.

- **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:** 12 May 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wc77-pp72-82qv

## What is CVE-2010-0816?

CVE-2010-0816 is a critical vulnerability in n/a, published on 12 May 2010. 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 inetcomm.dll in Microsoft Outlook Express 5.5 SP2, 6, and 6 SP1; Windows Live Mail on Windows XP SP2 and SP3, Windows Vista SP1 and SP2, Windows Server 2008 Gold, SP2, and R2, and Windows 7; and Windows Mail on Windows Vista SP1 and SP2, Windows Server 2008 Gold, SP2, and R2, and Windows 7 allows remote e-mail servers and man-in-the-middle attackers to execute arbitrary code via a crafted (1) POP3 or (2) IMAP response, as demonstrated by a certain +OK response on TCP port 110, aka "Outlook Express and Windows Mail Integer Overflow Vulnerability."

Weakness: CWE-189

## Which versions are affected by CVE-2010-0816?

It affects 3 products.


Products: Microsoft Outlook Express, Microsoft Windows Live Mail, Microsoft Windows Mail.

## How do I fix CVE-2010-0816?

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

## Is CVE-2010-0816 being exploited?

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

Public exploit code:

- Microsoft Windows Outlook Express and Windows Mail - Integer Overflow (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2004-0380](https://insights.sbomify.com/CVE-2004-0380/): Security feature bypass in n/a (critical 10.0)
- [CVE-2010-3147](https://insights.sbomify.com/CVE-2010-3147/): Path traversal in n/a (critical 9.3)
- [CVE-2007-3897](https://insights.sbomify.com/CVE-2007-3897/): Memory corruption in n/a (critical 9.3)
- [CVE-2001-1547](https://insights.sbomify.com/CVE-2001-1547/): Security feature bypass in n/a (high 7.5)
- [CVE-2005-1213](https://insights.sbomify.com/CVE-2005-1213/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-0816 and fix it if it is affected.

What it is: CVE-2010-0816 is a critical vulnerability in n/a, published on 12 May 2010. 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-2010-0816 exists.

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-2010-0816/ (Markdown: https://insights.sbomify.com/CVE-2010-0816/index.md)
```

## Sources

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

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