# CVE-2007-1754: Memory corruption in n/a

> Remote attackers can execute arbitrary code by tricking users into opening a malformed Publisher file that triggers a memory corruption vulnerability.

- **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:** 10 Jul 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7chc-jmhv-g4m2

## What is CVE-2007-1754?

CVE-2007-1754 is a critical memory corruption vulnerability in n/a, published on 10 Jul 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

PUBCONV.DLL in Microsoft Office Publisher 2007 does not properly clear memory when transferring data from disk to memory, which allows user-assisted remote attackers to execute arbitrary code via a malformed .pub page via a certain negative value, which bypasses a sanitization procedure that initializes critical pointers to NULL, aka the "Publisher Invalid Memory Reference Vulnerability".

Weakness: CWE-399

## Which versions are affected by CVE-2007-1754?

It affects 1 product.


Products: Microsoft Publisher.

## How do I fix CVE-2007-1754?

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

## Is CVE-2007-1754 being exploited?

There is no known exploitation of CVE-2007-1754 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-2007-1754 and fix it if it is affected.

What it is: CVE-2007-1754 is a critical memory corruption vulnerability in n/a, published on 10 Jul 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-2007-1754 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-2007-1754/ (Markdown: https://insights.sbomify.com/CVE-2007-1754/index.md)
```

## Sources

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

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