dbcve.org
Mp3gainApplication

CVE-2017-12911

MEDIUM · 5.5 CVSS v3.0 Published 2017-09-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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
The "apetag.c" file in MP3Gain 1.5.2.r2 has a vulnerability which results in a stack memory corruption when opening 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 confidence

Stack memory corruption vulnerability in MP3Gain 1.5.2.r2's APE tag parser (apetag.c) triggered when opening a crafted MP3 file with malformed APE metadata. The vulnerability allows potential code execution via stack buffer overflow during tag parsing.

MitigationDo not open MP3 files from untrusted sources with MP3Gain until an official patch is released; implement bounds checking in APE tag parsing routines.

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
Mp3gainApplication
Affected:= 1.5.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
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 checks

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

  1. Verify MP3Gain is installed
    Run 'which mp3gain' on Linux/macOS or check common installation directories on Windows (e.g., C:\Program Files\MP3Gain, C:\Program Files (x86)\MP3Gain)
    Affected if MP3Gain executable is found on the system
  2. Determine the installed version
    Run 'mp3gain --version' or 'mp3gain -v' from the command line
    Affected if The reported version is exactly 1.5.2
  3. Confirm APE tag parsing is used
    Use MP3Gain to open or analyze an MP3 file that contains APE metadata tags (check with a hex editor or tag viewer for APE footer/header bytes starting with 'APETAGEX')
    Affected if MP3Gain parses APE tags from the target file
  4. Identify affected binary
    Locate the apetag.c component: on Linux check /usr/lib/mp3gain/ or the binary's linked libraries; on Windows check the installation folder for apetag.dll or verify the mp3gain.exe binary version
    Affected if The APE tag parsing module (apetag.c) version 1.5.2 is present

You are affected if MP3Gain version 1.5.2 is installed and you use it to open MP3 files containing APE metadata tags.

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

Do not open MP3 files from untrusted sources with MP3Gain until an official patch is released; implement bounds checking in APE tag parsing routines.

Fix this in Mp3gain Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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