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

> Remote attackers can execute arbitrary code or cause denial of service via a crafted Publisher file due to heap memory corruption in pubconv.dll.

- **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:** 16 Dec 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-q578-mw8r-r8v5

## What is CVE-2010-2569?

CVE-2010-2569 is a critical memory corruption vulnerability in n/a, published on 16 Dec 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

pubconv.dll (aka the Publisher Converter DLL) in Microsoft Publisher 2002 SP3, 2003 SP3, and 2007 SP2 does not properly handle an unspecified size field in certain older file formats, which allows remote attackers to execute arbitrary code or cause a denial of service (heap memory corruption) via a crafted Publisher file, aka "Size Value Heap Corruption in pubconv.dll Vulnerability."

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Microsoft Publisher.

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

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

## Is CVE-2010-2569 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-1318](https://insights.sbomify.com/CVE-2013-1318/): Memory corruption in n/a (critical 10.0)
- [CVE-2013-1319](https://insights.sbomify.com/CVE-2013-1319/): Memory corruption in n/a (critical 10.0)
- [CVE-2013-1320](https://insights.sbomify.com/CVE-2013-1320/): Memory corruption in n/a (critical 10.0)
- [CVE-2013-1322](https://insights.sbomify.com/CVE-2013-1322/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-0102](https://insights.sbomify.com/CVE-2008-0102/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-2569 is a critical memory corruption vulnerability in n/a, published on 16 Dec 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: There is no known exploitation of CVE-2010-2569 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-2010-2569/ (Markdown: https://insights.sbomify.com/CVE-2010-2569/index.md)
```

## Sources

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

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