# CVE-2010-5289: Memory corruption in n/a

> Remote attackers can trigger a buffer overflow in the IncrediMail ActiveX control via a long string, causing a crash or potential code execution.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 25 Aug 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-rj6f-6v3m-hmhr

## What is CVE-2010-5289?

CVE-2010-5289 is a high-severity memory corruption vulnerability in n/a, published on 25 Aug 2013. 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

Buffer overflow in the Authenticate method in the INCREDISPOOLERLib.Pop ActiveX control in ImSpoolU.dll in IncrediMail 2.0 allows remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via a long string in the first argument.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Incredimail Incredimail.

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

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

## Is CVE-2010-5289 being exploited?

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

Public exploit code:

- IncrediMail 2.0 - ActiveX (Authenticated) Buffer Overflow (PoC) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2002-0455](https://insights.sbomify.com/CVE-2002-0455/): Path traversal in n/a (medium 5.0)
- [CVE-2008-5429](https://insights.sbomify.com/CVE-2008-5429/): Denial of service in n/a (medium 4.3)
- [CVE-2001-0642](https://insights.sbomify.com/CVE-2001-0642/): Path traversal in n/a (low 2.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-5289 is a high-severity memory corruption vulnerability in n/a, published on 25 Aug 2013. 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-5289 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-5289/ (Markdown: https://insights.sbomify.com/CVE-2010-5289/index.md)
```

## Sources

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

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