# CVE-2004-2027: Memory corruption in n/a

> Remote attackers can crash the Icecast streaming server by sending a long Basic Authorization header, causing a denial of service.

- **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:** Yes
- **Published:** 10 May 2005
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2004-2027, GHSA-29fv-34jg-3cfg

## What is CVE-2004-2027?

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

### Official description

Buffer overflow in Icecast 2.0.0 and earlier allows remote attackers to cause a denial of service (crash) via a long Basic Authorization header that triggers an out-of-bounds read.

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

It affects 1 product.


Products: Icecast Icecast.

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

Upgrade to a fixed version.

## Is CVE-2004-2027 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2001-0197](https://insights.sbomify.com/CVE-2001-0197/): Code injection in n/a (critical 10.0)
- [CVE-2005-0838](https://insights.sbomify.com/CVE-2005-0838/): Memory corruption in n/a (high 7.5)
- [CVE-2004-1561](https://insights.sbomify.com/CVE-2004-1561/): Memory corruption in n/a (high 7.5)
- [CVE-2001-1229](https://insights.sbomify.com/CVE-2001-1229/): Memory corruption in n/a (high 7.5)
- [CVE-2001-1230](https://insights.sbomify.com/CVE-2001-1230/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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