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

> Attackers can cause a denial of service in the LAME MP3 encoder library by triggering a null pointer dereference in the ID3 tag processing function.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Aug 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-13712, GHSA-p3fq-hhf9-6f56, UBUNTU-CVE-2017-13712

## What is CVE-2017-13712?

CVE-2017-13712 is a high-severity vulnerability in n/a, published on 28 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NULL Pointer Dereference in the id3v2AddAudioDuration function in libmp3lame/id3tag.c in LAME 3.99.5 allows attackers to perform Denial of Service by triggering a NULL first argument.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Lame Project Lame.

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

Upgrade to a fixed version.

## Is CVE-2017-13712 being exploited?

There is no known exploitation of CVE-2017-13712 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-15019](https://insights.sbomify.com/CVE-2017-15019/): Null dereference in n/a (high 7.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)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-13712 is a high-severity vulnerability in n/a, published on 28 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-13712 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-13712/ (Markdown: https://insights.sbomify.com/CVE-2017-13712/index.md)
```

## Sources

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

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