dbcve.org
LibmodplugApplication · Konstanty Bialkowski

CVE-2011-2914

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
Off-by-one error in the CSoundFile::ReadDSM function in src/load_dms.cpp in libmodplug before 0.8.8.4 allows remote attackers to cause a denial of service (memory corruption) and possibly execute arbitrary code via a crafted DSM file with a large number of samples.

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

An off-by-one error in the CSoundFile::ReadDSM function in libmodplug's src/load_dms.cpp allows remote attackers to cause memory corruption via a crafted DSM file with a large number of samples, potentially leading to arbitrary code execution.

MitigationUpdate libmodplug to version 0.8.8.4 or later to obtain the patched code, or implement bounds checking in the ReadDSM function to validate sample count before memory allocation.

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. Identify libmodplug version
    Locate the libmodplug library file (libmodplug.so, libmodplug.dll, or static library) and check its version string, or inspect the version.h/source headers in a compiled version
    Affected if The installed version is 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, or any version <= 0.8.8.3 (including 0.8.8.3)
  2. Verify DSM file loading capability
    Check if your application or tool links against libmodplug and includes functionality to load or parse DSM audio files (check for DSM file format support in your media player, game, or audio processing tool)
    Affected if The application loads DSM files using libmodplug's ReadDSM function from src/load_dms.cpp
  3. Inspect vulnerable source file
    If you have access to the libmodplug source, locate src/load_dms.cpp and search for the ReadDSM function to confirm the off-by-one vulnerability exists in the code
    Affected if The source code contains the ReadDSM function without proper bounds checking on sample count before memory allocation

You are affected if your system has libmodplug version 0.8.8.3 or earlier (including all 0.8.x releases listed) and you load or process DSM audio files through an application using libmodplug.

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 obtain the patched code, or implement bounds checking in the ReadDSM function to validate sample count before memory allocation.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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