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

> Remote attackers can crash the server or execute arbitrary code via a long HTTP GET request in Sami HTTP Server.

- **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:** Not needed
- **Fix available:** No
- **Published:** 18 Mar 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-2g24-99jw-85x7

## What is CVE-2004-0292?

CVE-2004-0292 is a critical memory corruption vulnerability in n/a, published on 18 Mar 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in KarjaSoft Sami HTTP Server 1.0.4 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a long HTTP GET request.

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

It affects 1 product.


Products: Karjasoft Sami Http Server.

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

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

## Is CVE-2004-0292 being exploited?

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

Public exploit code:

- KarjaSoft Sami HTTP Server 1.0.4 - GET Buffer Overflow (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2021-4433](https://insights.sbomify.com/CVE-2021-4433/): Karjasoft Sami HTTP Server HTTP HEAD Rrequest denial of service (medium 5.3)
- [CVE-2007-0548](https://insights.sbomify.com/CVE-2007-0548/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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