# CVE-2001-1304: Memory corruption in n/a

> Remote attackers can crash SHOUTcast Server by sending HTTP requests with excessively long user-agent or host headers.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 May 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-3974-gm3f-4hv8

## What is CVE-2001-1304?

CVE-2001-1304 is a medium-severity memory corruption vulnerability in n/a, published on 3 May 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in SHOUTcast Server 1.8.2 allows remote attackers to cause a denial of service (crash) via several HTTP requests with a long (1) user-agent or (2) host HTTP header.

## Which versions are affected by CVE-2001-1304?

It affects 1 product.


Products: Nullsoft Shoutcast Server.

## How do I fix CVE-2001-1304?

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

## Is CVE-2001-1304 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-3534](https://insights.sbomify.com/CVE-2006-3534/): Path traversal in n/a (high 7.8)
- [CVE-2004-1373](https://insights.sbomify.com/CVE-2004-1373/): Memory corruption in n/a (high 7.5)
- [CVE-2002-0907](https://insights.sbomify.com/CVE-2002-0907/): Memory corruption in n/a (high 7.5)
- [CVE-2002-0199](https://insights.sbomify.com/CVE-2002-0199/): Memory corruption in n/a (high 7.5)
- [CVE-1999-1561](https://insights.sbomify.com/CVE-1999-1561/): Hardcoded credentials in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-1304 and fix it if it is affected.

What it is: CVE-2001-1304 is a medium-severity memory corruption vulnerability in n/a, published on 3 May 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2001-1304 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-2001-1304/ (Markdown: https://insights.sbomify.com/CVE-2001-1304/index.md)
```

## Sources

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

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