CVE-2006-4513
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMultiple 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceInteger overflow vulnerabilities in the WV library's wvGetLFO_records and wvGetFLO_PLF functions allow crafted DOC files with oversized LFO nolfo or clfolvl values to trigger heap-based buffer overflows during memory allocation, potentially enabling arbitrary code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.2.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:H/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check wvWare package versionRun 'rpm -qa | grep wv' (RHEL/CentOS) or 'dpkg -l | grep wv' (Debian/Ubuntu) to list installed wv packagesAffected if The installed version is 1.2.2 or lower
-
Check wv library versionRun 'ldconfig -p | grep wv' to locate the wv shared library, then use 'strings <library_path> | grep -i version' or check the file metadataAffected if The wv library binary reports version 1.2.2 or lower
-
Identify wv-enabled applicationsCheck installed applications that depend on wv: run 'rpm -qa | grep -i abiword' or 'dpkg -l | grep abiword' for AbiWord, and similar queries for KWord or other products using the wv libraryAffected if Any wv-dependent application (AbiWord, KWord, etc.) is installed alongside wv library version 1.2.2 or lower
-
Check for wvConvert or wvWare binariesLocate wv executables with 'which wvWare' or 'which wvConvert', then run '--version' on them if availableAffected if The binary version is 1.2.2 or lower
The environment is affected if the wv library or wvWare package is installed at version 1.2.2 or lower, as this version contains the integer overflow in wvGetLFO_records and wvGetFLO_PLF functions that triggers during DOC file processing.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade wvWare/wv library to version 1.2.3 or later; apply vendor patches for AbiWord, KWord, or other affected products; avoid opening untrusted Word documents until patches are applied.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-4513 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2006-4513 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data