# CVE-2017-14412: Memory corruption in n/a

> An invalid memory write in the mpglibDBL library allows attackers to cause a denial of service via a segmentation fault.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 13 Sep 2017
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2017-14412, GHSA-jhxc-486q-x8hm

## What is CVE-2017-14412?

CVE-2017-14412 is a high-severity memory corruption vulnerability in n/a, published on 13 Sep 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2017-14412?

It affects 1 product.


Products: Mp3gain Mp3gain.

## How do I fix CVE-2017-14412?

Apply the vendor's patch.

## Is CVE-2017-14412 being exploited?

There is no known exploitation of CVE-2017-14412 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2018-10776](https://insights.sbomify.com/CVE-2018-10776/): Denial of service in n/a (high 7.8)
- [CVE-2018-10777](https://insights.sbomify.com/CVE-2018-10777/): Memory corruption in n/a (high 7.8)
- [CVE-2018-10778](https://insights.sbomify.com/CVE-2018-10778/): Memory corruption in n/a (high 7.8)
- [CVE-2017-14409](https://insights.sbomify.com/CVE-2017-14409/): Memory corruption in n/a (high 7.8)
- [CVE-2017-14411](https://insights.sbomify.com/CVE-2017-14411/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-14412 and fix it if it is affected.

What it is: CVE-2017-14412 is a high-severity memory corruption vulnerability in n/a, published on 13 Sep 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-14412 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-14412/ (Markdown: https://insights.sbomify.com/CVE-2017-14412/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-14412
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-14412
- OSV: https://osv.dev/vulnerability/CVE-2017-14412

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-14412/
Summaries are generated and may contain mistakes; the official description above is the record.