# CVE-2004-1302: Command injection in n/a

> Remote attackers can execute arbitrary commands by tricking users into opening a malicious MP3 file with crafted Artist tags in YAMT.

- **Severity:** Critical 10.0 (`AV:N/AC:L/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:** 22 Dec 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-59q6-5qj6-cxp2

## What is CVE-2004-1302?

CVE-2004-1302 is a critical command injection vulnerability in n/a, published on 22 Dec 2004. 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

The id3tag_sort function in id3tag.c for YAMT 0.5 allows remote attackers to execute arbitrary commands via an MP3 file with double quotes in the Artist tag.

## Which versions are affected by CVE-2004-1302?

It affects 1 product.


Products: Yamt Yamt.

## How do I fix CVE-2004-1302?

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

## Is CVE-2004-1302 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-1847](https://insights.sbomify.com/CVE-2005-1847/): Memory corruption in n/a (high 7.5)
- [CVE-2005-1846](https://insights.sbomify.com/CVE-2005-1846/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-1302 and fix it if it is affected.

What it is: CVE-2004-1302 is a critical command injection vulnerability in n/a, published on 22 Dec 2004. 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-2004-1302 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-2004-1302/ (Markdown: https://insights.sbomify.com/CVE-2004-1302/index.md)
```

## Sources

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

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