CVE-2016-9265
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 · uneditedThe printMP3Headers function in listmp3.c in Libming 0.4.7 allows remote attackers to cause a denial of service (divide-by-zero error and application crash) via a crafted mp3 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 · moderate confidenceA divide-by-zero vulnerability exists in the printMP3Headers function in listmp3.c of Libming 0.4.7. When processing a specially crafted MP3 file, the function attempts to perform a division operation where the divisor can be controlled to be zero, causing the application to crash. This results in a denial-of-service condition exploitable by remote attackers who can supply the malicious file.
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= 0.4.7CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
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 if Libming is installedRun 'pkg-config --modversion libming' or check your system's package manager for libming packagesAffected if Libming version 0.4.7 is installed
-
Verify the exact Libming versionRun 'ming-listmp3 -V' or check the library file version if available, compare against 0.4.7Affected if The installed version is exactly 0.4.7
-
Identify if the listmp3 utility existsCheck for the presence of 'ming-listmp3' binary on the system using 'which ming-listmp3' or file system searchAffected if The ming-listmp3 utility is present and linked against Libming 0.4.7
-
Determine if untrusted MP3 files are processedReview application logs or configuration to see if MP3 files from external/untrusted sources are processed by Libming toolsAffected if Applications process MP3 files from untrusted sources using Libming
-
Inspect for crash logs related to MP3 processingSearch system/application logs and crash reports for divide-by-zero errors or SIGFPE signals during MP3 header parsingAffected if Recent crashes show SIGFPE or divide-by-zero errors when processing MP3 files
A system is affected if Libming version 0.4.7 is installed and processes untrusted MP3 files with the printMP3Headers function from listmp3.c.
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 dataUpdate to a patched version of Libming if available, or implement input validation in the printMP3Headers function to verify the divisor is non-zero before performing division operations. Sanitize or reject MP3 files with malformed headers that could trigger the divide-by-zero condition.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-9265 — 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-2016-9265 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