# CVE-2005-2806: Denial of service in n/a

> Remote attackers can cause a denial of service in BNBT EasyTracker by sending a malformed HTTP header, potentially triggering an integer signedness error.

- **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:** 6 Sep 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8pr9-gcwm-r2q9

## What is CVE-2005-2806?

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

### Official description

client.cpp in BNBT EasyTracker 7.7r3.2004.10.27 and earlier allows remote attackers to cause a denial of service (application hang) via an HTTP header containing only a ":" (colon), possibly leading to an integer signedness error due to a missing field name or value.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2005-2806?

It affects 1 product.


Products: Trevor Hogan Bnbt.

## How do I fix CVE-2005-2806?

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

## Is CVE-2005-2806 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-2029](https://insights.sbomify.com/CVE-2004-2029/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2806 and fix it if it is affected.

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

## Sources

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

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