# CVE-2006-3124: Memory corruption in n/a

> Remote attackers can cause denial of service or execute arbitrary code via crafted HTTP headers in Streamripper.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/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:** 26 Aug 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-3124, DSA-1158, GHSA-jrqj-hpcm-6c55

## What is CVE-2006-3124?

CVE-2006-3124 is a high-severity memory corruption vulnerability in n/a, published on 26 Aug 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in the HTTP header parsing in Streamripper before 1.61.26 allows remote attackers to cause a denial of service and possibly execute arbitrary code via crafted HTTP headers.

## Which versions are affected by CVE-2006-3124?

It affects 1 product.


Products: Streamripper Streamripper.

## How do I fix CVE-2006-3124?

Upgrade to a fixed version.

## Is CVE-2006-3124 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-3124 exists.

Public exploit code:

- Streamripper 1.61.25 - HTTP Header Parsing Buffer Overflow (1) (exploitdb)
- Streamripper 1.61.25 - HTTP Header Parsing Buffer Overflow (2) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-4829](https://insights.sbomify.com/CVE-2008-4829/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-4337](https://insights.sbomify.com/CVE-2007-4337/): Multiple buffer overflows in the httplib_parse_sc_header function in lib/http.c in Streamripper before 1.62.2 allow remote attackers to exec (medium 5.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-3124 and fix it if it is affected.

What it is: CVE-2006-3124 is a high-severity memory corruption vulnerability in n/a, published on 26 Aug 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-3124 exists.

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-2006-3124/ (Markdown: https://insights.sbomify.com/CVE-2006-3124/index.md)
```

## Sources

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

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