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

> A buffer overflow in libopenmpt's C API allows attackers to execute arbitrary code or cause denial of service via crafted audio files.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 3 Oct 2019
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-17113, DLA-2308-1, GHSA-9qmp-r7mf-m39c, SUSE-SU-2019:2622-1, UBUNTU-CVE-2019-17113, USN-8206-1, openSUSE-SU-2019:2306-1, openSUSE-SU-2019:2319-1

## What is CVE-2019-17113?

CVE-2019-17113 is a critical memory corruption vulnerability in n/a, published on 3 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In libopenmpt before 0.3.19 and 0.4.x before 0.4.9, ModPlug_InstrumentName and ModPlug_SampleName in libopenmpt_modplug.c do not restrict the lengths of libmodplug output-buffer strings in the C API, leading to a buffer overflow.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libopenmpt` | SUSE:Linux Enterprise Module for Desktop Applications 15 | All versions | 0.3.19-2.10.1 |
| `libopenmpt` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP1 | All versions | 0.3.19-2.10.1 |
| `libopenmpt` | openSUSE:Leap 15.0 | All versions | 0.3.19-lp150.10.1 |
| `libopenmpt` | openSUSE:Leap 15.1 | All versions | 0.3.19-lp151.2.6.1 |

Products: Openmpt Libopenmpt.

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

Upgrade to a fixed version.

## Is CVE-2019-17113 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-11710](https://insights.sbomify.com/CVE-2018-11710/): Memory corruption in n/a (high 8.8)
- [CVE-2018-6611](https://insights.sbomify.com/CVE-2018-6611/): Memory corruption in n/a (high 8.8)
- [CVE-2017-11311](https://insights.sbomify.com/CVE-2017-11311/): Memory corruption in n/a (high 7.8)
- [CVE-2019-14381](https://insights.sbomify.com/CVE-2019-14381/): Null dereference in n/a (high 7.5)
- [CVE-2018-20860](https://insights.sbomify.com/CVE-2018-20860/): Denial of service in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-17113 is a critical memory corruption vulnerability in n/a, published on 3 Oct 2019. 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-2019-17113 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-17113/ (Markdown: https://insights.sbomify.com/CVE-2019-17113/index.md)
```

## Sources

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

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