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

> Remote attackers can cause a denial of service via a crafted file due to uninitialized data usage in Libmp3splt.

- **Severity:** Medium 5.0 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 9 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-15185, GHSA-6q92-h9xw-v5pf, UBUNTU-CVE-2017-15185

## What is CVE-2017-15185?

CVE-2017-15185 is a medium-severity vulnerability in n/a, published on 9 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

plugins/ogg.c in Libmp3splt 0.9.2 calls the libvorbis vorbis_block_clear function with uninitialized data upon detection of invalid input, which allows remote attackers to cause a denial of service (application crash) via a crafted file.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Libmp3splt Project Libmp3splt.

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

Apply the vendor's patch.

## Is CVE-2017-15185 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-5665](https://insights.sbomify.com/CVE-2017-5665/): Null dereference in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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