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

> An integer overflow in OpenOffice.org allows remote attackers to crash the application via a crafted DOC file, requiring user interaction.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:N/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:** 18 Dec 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-gj93-5m6j-gvr2

## What is CVE-2006-6628?

CVE-2006-6628 is a medium-severity vulnerability in n/a, published on 18 Dec 2006. 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 OpenOffice.org (OOo) 2.1 allows user-assisted remote attackers to cause a denial of service (application crash) via a crafted DOC file, as demonstrated by the 12122006-djtest.doc file, a variant of CVE-2006-6561 in a separate codebase.

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

It affects 1 product.


Products: Openoffice Openoffice.

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

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

## Is CVE-2006-6628 being exploited?

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

Public exploit code:

- Microsoft Word Document - Malformed Pointer (PoC) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-4575](https://insights.sbomify.com/CVE-2007-4575/): Code injection in n/a (critical 9.3)
- [CVE-2007-0245](https://insights.sbomify.com/CVE-2007-0245/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-0238](https://insights.sbomify.com/CVE-2007-0238/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-0239](https://insights.sbomify.com/CVE-2007-0239/): Command injection in n/a (critical 9.3)
- [CVE-2006-5870](https://insights.sbomify.com/CVE-2006-5870/): Integer overflow in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-6628 is a medium-severity vulnerability in n/a, published on 18 Dec 2006. 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-2006-6628 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-2006-6628/ (Markdown: https://insights.sbomify.com/CVE-2006-6628/index.md)
```

## Sources

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

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