# CVE-2017-15019: Null dereference in n/a

> A NULL pointer dereference in LAME allows attackers to cause a denial of service via a malformed MP3 file.

- **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:** 4 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-15019, GHSA-75h9-f495-r8mw, UBUNTU-CVE-2017-15019

## What is CVE-2017-15019?

CVE-2017-15019 is a high-severity vulnerability in n/a, published on 4 Oct 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

LAME 3.99.5 has a NULL Pointer Dereference in the hip_decode_init function within libmp3lame/mpglib_interface.c via a malformed mpg file, because of an incorrect calloc call.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Lame Project Lame.

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

Upgrade to a fixed version.

## Is CVE-2017-15019 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-11720](https://insights.sbomify.com/CVE-2017-11720/): Denial of service in n/a (critical 9.8)
- [CVE-2017-9871](https://insights.sbomify.com/CVE-2017-9871/): Memory corruption in n/a (high 7.8)
- [CVE-2017-9872](https://insights.sbomify.com/CVE-2017-9872/): Memory corruption in n/a (high 7.8)
- [CVE-2017-8419](https://insights.sbomify.com/CVE-2017-8419/): Memory corruption in n/a (high 7.8)
- [CVE-2017-13712](https://insights.sbomify.com/CVE-2017-13712/): Null dereference in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-15019 is a high-severity vulnerability in n/a, published on 4 Oct 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-15019 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-15019/ (Markdown: https://insights.sbomify.com/CVE-2017-15019/index.md)
```

## Sources

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

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