# CVE-2009-4201: Memory corruption in n/a

> Remote attackers can execute arbitrary code by tricking users into opening a malicious MP3 file with oversized metadata fields.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **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:** No
- **Published:** 4 Dec 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hxjf-xrrg-3wch

## What is CVE-2009-4201?

CVE-2009-4201 is a critical memory corruption vulnerability in n/a, published on 4 Dec 2009. 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

Multiple stack-based buffer overflows in Mp3 Tag Assistant Professional 2.92 build 300 allow remote attackers to execute arbitrary code via an MP3 file with a long string in the (1) ID3v1, (2) ID3v2, or (3) APEv2 metadata field.

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

## Which versions are affected by CVE-2009-4201?

It affects 1 product.


Products: Assistanttools Mp3 Tag Assistance Professional.

## How do I fix CVE-2009-4201?

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

## Is CVE-2009-4201 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-4201 and fix it if it is affected.

What it is: CVE-2009-4201 is a critical memory corruption vulnerability in n/a, published on 4 Dec 2009. 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-2009-4201 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-2009-4201/ (Markdown: https://insights.sbomify.com/CVE-2009-4201/index.md)
```

## Sources

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

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