# CVE-2010-2195: Denial of service in n/a

> Attackers can cause a denial of service in the bozohttpd HTTP server due to a compiler interaction issue.

- **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:** 2 Aug 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-q76f-hqqv-cqmv

## What is CVE-2010-2195?

CVE-2010-2195 is a medium-severity denial of service vulnerability in n/a, published on 2 Aug 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

bozotic HTTP server (aka bozohttpd) 20090522 through 20100512 allows attackers to cause a denial of service via vectors related to a "wrong code generation interaction with GCC."

## Which versions are affected by CVE-2010-2195?

It affects 1 product.


Products: Eterna Bozohttpd.

## How do I fix CVE-2010-2195?

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

## Is CVE-2010-2195 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-5015](https://insights.sbomify.com/CVE-2014-5015/): Auth bypass in n/a (medium 5.0)
- [CVE-2010-2320](https://insights.sbomify.com/CVE-2010-2320/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-2195 and fix it if it is affected.

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

## Sources

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

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