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

> Remote attackers can cause a denial of service via memory corruption in libmad when processing crafted MP3 files with mpg321.

- **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:** 1 Aug 2017
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2017-11552, DEBIAN-CVE-2017-11552, GHSA-m9v2-ffx5-rxfq, UBUNTU-CVE-2017-11552

## What is CVE-2017-11552?

CVE-2017-11552 is a medium-severity memory corruption vulnerability in n/a, published on 1 Aug 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

mpg321.c in mpg321 0.3.2-1 does not properly manage memory for use with libmad 0.15.1b, which allows remote attackers to cause a denial of service (memory corruption seen in a crash in the mad_decoder_run function in decoder.c in libmad) via a crafted MP3 file.

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

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

It affects 1 product.


Products: Underbit Mad Libmad.

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

Apply the vendor's patch.

## Is CVE-2017-11552 being exploited?

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

Public exploit code:

- libmad 0.15.1b - 'mp3' Memory Corruption (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2017-8373](https://insights.sbomify.com/CVE-2017-8373/): Memory corruption in n/a (high 7.8)
- [CVE-2017-8374](https://insights.sbomify.com/CVE-2017-8374/): Memory corruption in n/a (medium 5.5)
- [CVE-2017-8372](https://insights.sbomify.com/CVE-2017-8372/): Denial of service in n/a (medium 4.7)

## Fix prompt for AI coding agents

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

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

## Sources

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

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