# CVE-2019-14247: Memory corruption in n/a

> Remote attackers can trigger an out-of-bounds write via a malicious MP3 file, potentially leading to code execution or denial of service.

- **Severity:** Medium 5.5 (`CVSS:3.0/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:** 24 Jul 2019
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-14247, GHSA-m9vf-222p-8grm, UBUNTU-CVE-2019-14247

## What is CVE-2019-14247?

CVE-2019-14247 is a medium-severity memory corruption vulnerability in n/a, published on 24 Jul 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

The scan() function in mad.c in mpg321 0.3.2 allows remote attackers to trigger an out-of-bounds write via a zero bitrate in an MP3 file.

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

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

It affects 1 product.


Products: Mpg321 Project Mpg321.

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

Apply the vendor's patch.

## Is CVE-2019-14247 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-14247 is a medium-severity memory corruption vulnerability in n/a, published on 24 Jul 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: There is no known exploitation of CVE-2019-14247 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-2019-14247/ (Markdown: https://insights.sbomify.com/CVE-2019-14247/index.md)
```

## Sources

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

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