dbcve.org
Mp3gainApplication

CVE-2017-14412

HIGH · 7.8 CVSS v3.0 Published 2017-09-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
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
An invalid memory write was discovered in copy_mp in interface.c in mpglibDBL, as used in MP3Gain version 1.5.2. The vulnerability causes a denial of service (segmentation fault and application crash) or possibly unspecified other impact.

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

A buffer overflow vulnerability exists in the copy_mp function in interface.c within the mpglibDBL library used by MP3Gain 1.5.2. The invalid memory write allows an attacker to trigger a denial of service via segmentation fault, with potential for unspecified other impact.

MitigationUpgrade to a patched version of MP3Gain if available, or implement bounds checking in the copy_mp function to validate buffer sizes before memory operations.

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
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 installation
    Check if MP3Gain is installed on the system by running 'mp3gain --version' or checking the application binary
    Affected if MP3Gain is present and version 1.5.2 is returned
  2. Confirm exact version number
    Run 'mp3gain -v' or 'mp3gain --version' to obtain the precise version string
    Affected if The version reported is exactly 1.5.2
  3. Identify the vulnerable library
    Locate the mpglibDBL library (typically embedded in or linked with the MP3Gain binary) - check the binary or shared object for references to 'mpglibDBL' and 'copy_mp' function
    Affected if The copy_mp function from mpglibDBL library is present in the installed version
  4. Determine if processing of untrusted MP3 files is possible
    Check if MP3Gain can be invoked to process MP3 files - the vulnerability triggers when the copy_mp function processes crafted MP3 data
    Affected if Users can run MP3Gain to process MP3 files using the affected version

The environment is affected if MP3Gain version 1.5.2 is installed and can be used to process MP3 files, as this triggers the vulnerable copy_mp function in the mpglibDBL library.

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

Upgrade to a patched version of MP3Gain if available, or implement bounds checking in the copy_mp function to validate buffer sizes before memory operations.

Fix this in Mp3gain Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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