# CVE-2016-9266: Integer overflow in n/a

> A crafted MP3 file triggers an invalid left shift in libming, potentially causing a denial of service.

- **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:** 23 Mar 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2mxf-cwcv-jcx7, UBUNTU-CVE-2016-9266

## What is CVE-2016-9266?

CVE-2016-9266 is a medium-severity vulnerability in Libming Libming, published on 23 Mar 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

listmp3.c in libming 0.4.7 allows remote attackers to unspecified impact via a crafted mp3 file, which triggers an invalid left shift.

Weakness: CWE-189

## Which versions are affected by CVE-2016-9266?

It affects 1 product.


Products: Libming Libming.

## How do I fix CVE-2016-9266?

Upgrade to a fixed version.

## Is CVE-2016-9266 being exploited?

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

## Other vulnerabilities in Libming Libming

- [CVE-2023-50628](https://insights.sbomify.com/CVE-2023-50628/): Memory corruption in n/a (critical 9.8)
- [CVE-2020-11894](https://insights.sbomify.com/CVE-2020-11894/): Memory corruption in n/a (critical 9.1)
- [CVE-2020-11895](https://insights.sbomify.com/CVE-2020-11895/): Memory corruption in n/a (critical 9.1)
- [CVE-2019-16705](https://insights.sbomify.com/CVE-2019-16705/): Information disclosure in n/a (critical 9.1)
- [CVE-2023-36239](https://insights.sbomify.com/CVE-2023-36239/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-9266 and fix it if it is affected.

What it is: CVE-2016-9266 is a medium-severity vulnerability in Libming Libming, published on 23 Mar 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-2016-9266 in the wild and no public exploit code.

Affected product: Libming Libming. 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-2016-9266/ (Markdown: https://insights.sbomify.com/CVE-2016-9266/index.md)
```

## Sources

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

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