# CVE-2019-18359: Denial of service in n/a

> A buffer over-read in MP3Gain allows remote attackers to cause a denial of service via a crafted MP3 file.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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:** 23 Oct 2019
- **Updated:** 15 Nov 2024
- **Also known as:** DEBIAN-CVE-2019-18359, GHSA-74ch-gqq9-g83c, MGASA-2020-0179

## What is CVE-2019-18359?

CVE-2019-18359 is a medium-severity denial of service vulnerability in n/a, published on 23 Oct 2019. 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

A buffer over-read was discovered in ReadMP3APETag in apetag.c in MP3Gain 1.6.2. The vulnerability causes an application crash, which leads to remote denial of service.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2019-18359?

It affects 1 product.


Products: Glensawyer Mp3gain.

## How do I fix CVE-2019-18359?

Apply the vendor's patch.

## Is CVE-2019-18359 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-18359 exists.

## Other vulnerabilities in n/a

- [CVE-2021-34085](https://insights.sbomify.com/CVE-2021-34085/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-49356](https://insights.sbomify.com/CVE-2023-49356/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-18359 and fix it if it is affected.

What it is: CVE-2019-18359 is a medium-severity denial of service vulnerability in n/a, published on 23 Oct 2019. 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-18359 exists.

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-2019-18359/ (Markdown: https://insights.sbomify.com/CVE-2019-18359/index.md)
```

## Sources

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

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