# CVE-2018-17095: Memory corruption in n/a

> A heap-based buffer overflow in the Audio File Library allows attackers to execute arbitrary code or cause denial of service via crafted audio files.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 16 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** AZL-45405, AZL-66252, DEBIAN-CVE-2018-17095, GHSA-p9gw-6qmw-52wh, MINI-q96r-9wmh-gg36, SUSE-SU-2018:3506-1, SUSE-SU-2018:3588-1, SUSE-SU-2018:3588-2, UBUNTU-CVE-2018-17095

## What is CVE-2018-17095?

CVE-2018-17095 is a high-severity memory corruption vulnerability in Canonical Ubuntu Linux, published on 16 Sep 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An issue has been discovered in mpruett Audio File Library (aka audiofile) 0.3.6, 0.3.5, 0.3.4, 0.3.3, 0.3.2, 0.3.1, 0.3.0. A heap-based buffer overflow in Expand3To4Module::run has occurred when running sfconvert.

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

## Which versions are affected by CVE-2018-17095?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `audiofile` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 0.3.6-11.3.1 |
| `audiofile` | SUSE:Linux Enterprise Desktop 12 SP4 | All versions | 0.3.6-11.3.1 |
| `audiofile` | SUSE:Linux Enterprise Module for Desktop Applications 15 | All versions | 0.3.6-3.3.1 |
| `audiofile` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 0.3.6-11.3.1 |
| `audiofile` | SUSE:Linux Enterprise Server 12 SP4 | All versions | 0.3.6-11.3.1 |
| `audiofile` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 0.3.6-11.3.1 |
| `audiofile` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 0.3.6-11.3.1 |
| `audiofile` | SUSE:Linux Enterprise Software Development Kit 12 SP3 | All versions | 0.3.6-11.3.1 |
| `audiofile` | SUSE:Linux Enterprise Software Development Kit 12 SP4 | All versions | 0.3.6-11.3.1 |

Products: Audiofile Audiofile, Canonical Ubuntu Linux.

## How do I fix CVE-2018-17095?

Apply the vendor's patch.

## Is CVE-2018-17095 being exploited?

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

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2015-7747](https://insights.sbomify.com/CVE-2015-7747/): Memory corruption in n/a (high 8.8)
- [CVE-2017-6827](https://insights.sbomify.com/CVE-2017-6827/): Memory corruption in n/a (high 7.8)
- [CVE-2017-6828](https://insights.sbomify.com/CVE-2017-6828/): Memory corruption in n/a (high 7.8)
- [CVE-2025-50950](https://insights.sbomify.com/CVE-2025-50950/): Null dereference in n/a (high 7.5)
- [CVE-2022-24599](https://insights.sbomify.com/CVE-2022-24599/): Information disclosure in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-17095 and fix it if it is affected.

What it is: CVE-2018-17095 is a high-severity memory corruption vulnerability in Canonical Ubuntu Linux, published on 16 Sep 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-17095 in the wild and no public exploit code.

Affected product: Canonical Ubuntu Linux. 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-2018-17095/ (Markdown: https://insights.sbomify.com/CVE-2018-17095/index.md)
```

## Sources

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

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