# CVE-2014-9497: Buffer overflow in mpg123 before 1.18.0.


- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 29 Aug 2017
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-9497, GHSA-fpx3-552f-qj3v, UBUNTU-CVE-2014-9497

## What is CVE-2014-9497?

CVE-2014-9497 is a high-severity vulnerability in n/a, published on 29 Aug 2017. 

### Official description

Buffer overflow in mpg123 before 1.18.0.

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

## Which versions are affected by CVE-2014-9497?

It affects 1 product.


Products: Mpg123 Mpg123.

## How do I fix CVE-2014-9497?

Upgrade to a fixed version.

## Is CVE-2014-9497 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-1301](https://insights.sbomify.com/CVE-2009-1301/): Integer overflow in n/a (critical 10.0)
- [CVE-2004-1284](https://insights.sbomify.com/CVE-2004-1284/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0982](https://insights.sbomify.com/CVE-2004-0982/): Memory corruption in n/a (critical 10.0)
- [CVE-2017-12839](https://insights.sbomify.com/CVE-2017-12839/): Memory corruption in n/a (high 8.3)
- [CVE-2017-10683](https://insights.sbomify.com/CVE-2017-10683/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-9497 and fix it if it is affected.

What it is: CVE-2014-9497 is a high-severity vulnerability in n/a, published on 29 Aug 2017. 
Exploitation: There is no known exploitation of CVE-2014-9497 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-2014-9497/ (Markdown: https://insights.sbomify.com/CVE-2014-9497/index.md)
```

## Sources

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

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