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

> Remote attackers can cause denial of service or potential code execution via a crafted file due to a heap-based buffer overflow in the WildMIDI library.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/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:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 2 Jan 2018
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2017-1000418, GHSA-fx9c-663j-cxhv

## What is CVE-2017-1000418?

CVE-2017-1000418 is a high-severity memory corruption vulnerability in n/a, published on 2 Jan 2018. 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 WildMidi_Open function in WildMIDI since commit d8a466829c67cacbb1700beded25c448d99514e5 allows remote attackers to cause a denial of service (heap-based buffer overflow and application crash) or possibly have unspecified other impact via a crafted file.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Mindwerks Wildmidi.

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

Apply the vendor's patch.

## Is CVE-2017-1000418 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-11661](https://insights.sbomify.com/CVE-2017-11661/): Denial of service in n/a (high 7.5)
- [CVE-2017-11662](https://insights.sbomify.com/CVE-2017-11662/): Denial of service in n/a (high 7.5)
- [CVE-2017-11663](https://insights.sbomify.com/CVE-2017-11663/): Denial of service in n/a (medium 6.5)
- [CVE-2017-11664](https://insights.sbomify.com/CVE-2017-11664/): Denial of service in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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