dbcve.org
LibmodplugApplication · Konstanty Bialkowski

CVE-2011-2915

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::ReadAMS2 function in src/load_ams.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 AMS file with a large number of instruments.

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

Off-by-one error in libmodplug's CSoundFile::ReadAMS2 function in src/load_ams.cpp allows memory corruption and potential code execution when parsing AMS files with a large number of instruments. The vulnerability stems from improper bounds checking when processing instrument data in the AMS file format.

MitigationUpdate libmodplug to version 0.8.8.4 or later which contains the fix for this vulnerability. Until then, avoid processing untrusted AMS files with applications using this library.

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 in your environment
    Search for libmodplug shared objects (libmodplug.so, libmodplug.a on Linux; modplug.lib, modplug.dll on Windows) in system library directories, application bundles, or within application binaries using ldd/dependency walker tools.
    Affected if The library is present on the system or linked into any application.
  2. Identify the installed libmodplug version
    Run 'pkg-config --modversion libmodplug' on Linux, check the DLL/so version properties on Windows, or examine the source version header if compiling locally. Also check any version strings embedded in the binary.
    Affected if Version cannot be determined or shows a version within the 0.8.x through 0.8.8.3 range.
  3. Determine if AMS file parsing is actively used
    Review application functionality to see if AMS file format support is enabled. AMS is a tracker music format. Check application documentation, file association settings, or runtime logs for AMS file processing activity.
    Affected if Applications process AMS files, especially those with many instruments.
  4. Compare version against affected range
    If a version is identified, verify it against: 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, or any version <= 0.8.8.3.
    Affected if Installed version matches any of the listed affected versions.

You are affected if libmodplug version 0.8 through 0.8.8.3 is present AND applications using this library process AMS files with many instruments.

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 which contains the fix for this vulnerability. Until then, avoid processing untrusted AMS files with applications using this library.

Fix this in Libmodplug Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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