# CVE-2017-11547: Memory corruption in n/a

> Remote attackers can cause a denial of service via a crafted MIDI file due to a heap-based buffer over-read in TiMidity++.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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:** 31 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-11547, GHSA-3jgw-g36w-mxm7, UBUNTU-CVE-2017-11547

## What is CVE-2017-11547?

CVE-2017-11547 is a medium-severity memory corruption vulnerability in n/a, published on 31 Jul 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

The resample_gauss function in resample.c in TiMidity++ 2.14.0 allows remote attackers to cause a denial of service (heap-based buffer over-read) via a crafted mid file. NOTE: a crash might be relevant when using the --background option. NOTE: the TiMidity++ README.alsaseq documentation suggests a setuid-root installation.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Timidity\+\+ Project Timidity\+\+.

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

Apply the vendor's patch.

## Is CVE-2017-11547 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-11546](https://insights.sbomify.com/CVE-2017-11546/): Denial of service in n/a (medium 5.5)
- [CVE-2017-11549](https://insights.sbomify.com/CVE-2017-11549/): The play_midi function in playmidi.c in TiMidity++ 2.14.0 allows remote attackers to cause a denial of service (large loop and CPU consumpti (medium 5.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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