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

> Attackers can execute arbitrary code or cause denial of service in Winamp via a crafted .flv file due to memory corruption.

- **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:** No
- **Published:** 5 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-85v5-mrc5-v3jh

## What is CVE-2017-10727?

CVE-2017-10727 is a high-severity memory corruption vulnerability in n/a, published on 5 Jul 2017. 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

Winamp 5.666 Build 3516(x86) might allow attackers to execute arbitrary code or cause a denial of service via a crafted .flv file, related to "Data from Faulting Address controls Branch Selection starting at in_mp3!DeleteAudioDecoder+0x000000000000762f."

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

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

It affects 1 product.


Products: Winamp Winamp.

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

No fix has been published for CVE-2017-10727 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-10727 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-4695](https://insights.sbomify.com/CVE-2013-4695/): Null dereference in n/a (high 7.8)
- [CVE-2017-10726](https://insights.sbomify.com/CVE-2017-10726/): Memory corruption in n/a (high 7.8)
- [CVE-2017-10728](https://insights.sbomify.com/CVE-2017-10728/): Memory corruption in n/a (high 7.8)
- [CVE-2017-10725](https://insights.sbomify.com/CVE-2017-10725/): Memory corruption in n/a (high 7.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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