# CVE-2017-17446: Integer overflow in n/a

> A remote attacker can cause a denial of service via a crafted file due to an integer overflow in the Game_Music_Emu library.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 6 Dec 2017
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2017-17446, GHSA-pwfg-g35m-wrcw, OESA-2022-1831, UBUNTU-CVE-2017-17446, USN-4816-1

## What is CVE-2017-17446?

CVE-2017-17446 is a medium-severity vulnerability in n/a, published on 6 Dec 2017. 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

The Mem_File_Reader::read_avail function in Data_Reader.cpp in the Game_Music_Emu library (aka game-music-emu) 0.6.1 does not ensure a non-negative size, which allows remote attackers to cause a denial of service (application crash) via a crafted file.

Weakness: CWE-681 (Incorrect Conversion between Numeric Types)

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

It affects 1 product.


Products: Game-Music-Emu Project Game-Music-Emu.

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

Upgrade to a fixed version.

## Is CVE-2017-17446 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-9957](https://insights.sbomify.com/CVE-2016-9957/): Memory corruption in n/a (high 7.8)
- [CVE-2016-9958](https://insights.sbomify.com/CVE-2016-9958/): Memory corruption in n/a (high 7.8)
- [CVE-2016-9959](https://insights.sbomify.com/CVE-2016-9959/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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