# CVE-2004-2117: Denial of service in n/a

> Remote attackers can crash Tiny Server by sending malformed HTTP requests, 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:** No
- **Published:** 27 May 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-mr95-v55h-pp97

## What is CVE-2004-2117?

CVE-2004-2117 is a medium-severity denial of service vulnerability in n/a, published on 27 May 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Tiny Server 1.1 allows remote attackers to cause a denial of service (crash) via malformed HTTP requests such as (1) a GET request without the HTTP version (HTTP/1.1), or (2) a request without GET or the HTTP version.

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

It affects 1 product.


Products: Tinyserver Tinyserver.

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

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

## Is CVE-2004-2117 being exploited?

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

Public exploit code:

- TinyServer 1.1 - Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2004-2116](https://insights.sbomify.com/CVE-2004-2116/): Path traversal in n/a (medium 5.0)
- [CVE-2004-2118](https://insights.sbomify.com/CVE-2004-2118/): Denial of service in n/a (medium 5.0)
- [CVE-2004-2119](https://insights.sbomify.com/CVE-2004-2119/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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