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

> Integer overflows in the WV library allow remote attackers to execute arbitrary code via a crafted Microsoft Word file, requiring user interaction to open the document.

- **Severity:** Medium 5.1 (`AV:N/AC:H/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:** Yes
- **Published:** 28 Oct 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-4513, GHSA-p252-96vf-v428

## What is CVE-2006-4513?

CVE-2006-4513 is a medium-severity vulnerability in n/a, published on 28 Oct 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

Multiple integer overflows in the WV library in wvWare (formerly mswordview) before 1.2.3, as used by AbiWord, KWord, and possibly other products, allow user-assisted remote attackers to execute arbitrary code via a crafted Microsoft Word (DOC) file that produces (1) large LFO clfolvl values in the wvGetLFO_records function or (2) a large LFO nolfo value in the wvGetFLO_PLF function.

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

It affects 1 product.


Products: Wvware Wvware.

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

Upgrade to a fixed version.

## Is CVE-2006-4513 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2006-4513 is a medium-severity vulnerability in n/a, published on 28 Oct 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: There is no known exploitation of CVE-2006-4513 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-2006-4513/ (Markdown: https://insights.sbomify.com/CVE-2006-4513/index.md)
```

## Sources

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

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