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

> Remote attackers can crash the Halo Combat Evolved server by sending a long client response due to an off-by-one 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:** 20 Feb 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-397w-gc7r-9x5j

## What is CVE-2004-1667?

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

### Official description

Off-by-one error in Halo Combat Evolved 1.04 and earlier allows remote attackers to cause a denial of service (server crash) via a long client response.

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

It affects 1 product.


Products: Gearbox Software Halo Combat Evolved.

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

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

## Is CVE-2004-1667 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-1741](https://insights.sbomify.com/CVE-2005-1741/): Denial of service in n/a (medium 5.0)
- [CVE-2004-1539](https://insights.sbomify.com/CVE-2004-1539/): Null dereference in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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