dbcve.org
LibwmfApplication · Wvware

CVE-2006-3376

HIGH · 7.5 CVSS v2.0 Published 2006-07-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Integer overflow in player.c in libwmf 0.2.8.4, as used in multiple products including (1) wv, (2) abiword, (3) freetype, (4) gimp, (5) libgsf, and (6) imagemagick allows remote attackers to execute arbitrary code via the MaxRecordSize header field in a WMF file.

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 · high confidence

Integer overflow in player.c within libwmf 0.2.8.4 allows remote attackers to execute arbitrary code via a crafted MaxRecordSize header field in WMF (Windows Metafile) files. The overflow can corrupt memory and enable code execution when parsing malicious WMF files in any application using the vulnerable libwmf library.

MitigationUpdate libwmf to a patched version (0.2.8.5 or later) and rebuild/redeploy all applications that link against it (wv, abiword, freetype, gimp, libgsf, imagemagick). Implement strict bounds checking on the MaxRecordSize header field before use in memory allocation calculations.

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
LibwmfApplication
Affected:= 0.2.8_.4
Wv2Application
Affected:= 0.2.1= 0.2.2= 0.2.3

CVSS 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
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check libwmf library version
    Run 'rpm -q libwmf' or 'dpkg -l libwmf' or check the library file directly with 'strings /usr/lib/libwmf.so.0 2>/dev/null | grep -i version' or check the package metadata with 'pkg-config --modversion libwmf'
    Affected if The installed version is exactly 0.2.8.4
  2. Check wv2 package version
    Run 'rpm -q wv2' or 'dpkg -l wv2' to list the installed version of the wv2 library package
    Affected if The installed version is 0.2.1, 0.2.2, or 0.2.3
  3. Identify applications linked against libwmf
    Run 'ldd $(which abiword gimp imagemagick 2>/dev/null) 2>/dev/null | grep wmf' or use 'ldconfig -p | grep wmf' to see which applications have libwmf loaded in memory
    Affected if Any application that processes WMF files is linked against a vulnerable libwmf version
  4. Detect WMF file handling capability
    Check if ImageMagick's 'identify' or 'convert' can handle WMF files by running 'identify -list format | grep -i wmf' or test with a sample WMF file
    Affected if ImageMagick or other tools report WMF file support and are linked to a vulnerable libwmf version

You are affected if libwmf version 0.2.8.4 or wv2 versions 0.2.1-0.2.3 are installed and any application using libwmf processes WMF files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update libwmf to a patched version (0.2.8.5 or later) and rebuild/redeploy all applications that link against it (wv, abiword, freetype, gimp, libgsf, imagemagick). Implement strict bounds checking on the MaxRecordSize header field before use in memory allocation calculations.

Fix this in Libwmf Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-3376 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2006-3376 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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