dbcve.org
LibmodplugApplication · Konstanty Bialkowski

CVE-2011-2911

MEDIUM · 6.8 CVSS v2.0 Published 2012-06-07
Fix available
A fix is available. Upgrade to after 0.8.8.3 or later.
See remediation →
77/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 the CSoundFile::ReadWav function in src/load_wav.cpp in libmodplug before 0.8.8.4 allows remote attackers to cause a denial of service and possibly execute arbitrary code via a crafted WAV file, which triggers a heap-based buffer overflow.

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 libmodplug's CSoundFile::ReadWav function allows attackers to trigger a heap-based buffer overflow via crafted WAV files, potentially enabling arbitrary code execution.

MitigationUpdate libmodplug to version 0.8.8.4 or later to patch the integer overflow vulnerability in WAV file parsing.

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
LibmodplugApplication
Affected:<= 0.8.8.3= 0.8= 0.8.4= 0.8.5= 0.8.6= 0.8.7= 0.8.8= 0.8.8.1= 0.8.8.2

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

AV:N/AC:M/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. Locate libmodplug library on the system
    Search for libmodplug shared object files (e.g., libmodplug.so, libmodplug.so.1, libmodplug.so.0) using 'find /usr -name "libmodplug*" 2>/dev/null' or check package management tools like 'dpkg -l | grep modplug' (Debian) or 'rpm -qa | grep modplug' (RPM-based)
    Affected if libmodplug library is found on the system
  2. Determine installed libmodplug version
    Run 'pkg-config --modversion modplug' or check the library filename (often includes version in symlink like libmodplug.so.0.8.8.3), or use package query commands
    Affected if The version number is 0.8.8.3 or lower, or matches any of these: 0.8, 0.8.4, 0.8.5, 0.8.6, 0.8.7, 0.8.8, 0.8.8.1, 0.8.8.2, 0.8.8.3
  3. Identify applications using libmodplug
    Run 'ldd $(which <application>) | grep modplug' on suspected media players (e.g., Amarok, XMMS, VLC may link to libmodplug) or search process memory for loaded libmodplug with 'grep -l libmodplug /proc/*/maps 2>/dev/null'
    Affected if Any application has libmodplug loaded in memory and processes audio files
  4. Check if WAV file processing is in use
    Review application logs, configuration, or user behavior to determine if WAV files are being opened or converted, or monitor for file access to .wav extensions
    Affected if The libmodplug-using application processes WAV files, either directly or as part of a conversion pipeline

A system is affected if libmodplug version 0.8.8.3 or lower is installed AND any application uses libmodplug to process WAV files, enabling the integer overflow in ReadWav to be triggered by a crafted WAV file.

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
Upgrade available Upgrade to a release after 0.8.8.3
Interim mitigation

Update libmodplug to version 0.8.8.4 or later to patch the integer overflow vulnerability in WAV file parsing.

Fix this in Libmodplug Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-2911 — 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-2011-2911 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