CVE-2004-1539: Halo: Combat Evolved 1.05 and earlier allows remote game servers to cause a denial of service (client crash) v

This month

MEDIUM 5.0DOWNGRADE

CVE-2004-1539 is a medium-severity flaw (CVSS 5.0) affecting halo combat evolved. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Halo: Combat Evolved 1.05 and earlier allows remote game servers to cause a denial of service (client crash) via a long value in a game server reply, which triggers a NULL dereference.

Why this priority

Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	5.0 (Medium)
EPSS exploit chance	3.4% (top 11%)
CISA exploited list	No
Published	2004-12-31
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: gearbox software

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2004-12-31 05:00 UTCPublished CVE record published
2026-06-16 22:07 UTCUpdated Record last modified

gearbox software halo combat evolved DOWNGRADE

Affected: 1.2 · 1.4 · 1.5 · 1.31

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.2

1. Check installed version

apt-cache policy halo-combat-evolved || rpm -q halo-combat-evolved || halo-combat-evolved --version

2. No fixed release: DOWNGRADE to a release before 1.2 (Debian / Ubuntu)

apt-cache madison halo-combat-evolved sudo apt install halo-combat-evolved=<VERSION_BEFORE_1.2> sudo apt-mark hold halo-combat-evolved

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list halo-combat-evolved sudo dnf downgrade halo-combat-evolved-<VERSION_BEFORE_1.2> sudo dnf versionlock add halo-combat-evolved

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Exploit-DB: Halo 1.05 - Broadcast Client Crash

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2004-1539?

halo combat evolved: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2004-1539 being exploited?

CVE-2004-1539 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2004-1539 affect?

CVE-2004-1539 affects halo combat evolved. Severity is medium (CVSS 5.0). Halo: Combat Evolved 1.05 and earlier allows remote game servers to cause a denial of service (client crash) via a long value in a game server reply, which triggers a NULL dereference.

How urgent is CVE-2004-1539?

Priority 45/100. Public exploit reference

Related CVEs

CVE-2005-1741 MEDIUM 5.0 DOWNGRADE Gearbox Software Halo: Combat Evolved 1.6 allows remote attackers to cause a denial of service (infinite loop)
CVE-2004-1667 MEDIUM 5.0 DOWNGRADE Off-by-one error in Halo Combat Evolved 1.04 and earlier allows remote attackers to cause a denial of service

References

← Back to latest CVEs