CVE-2004-1869: Etherlords I 1.07 and earlier and Etherlords II 1.03 and earlier allows remote attackers to cause a denial of

This month

MEDIUM 5.0DOWNGRADEDOWNGRADE

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

Etherlords I 1.07 and earlier and Etherlords II 1.03 and earlier allows remote attackers to cause a denial of service (crash) by sending a packet that specifies the size for the next packet, then sending a larger packet than specified, which causes Etherlords to read unallocated memory.

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	1.7% (top 23%)
CISA exploited list	No
Published	2004-12-31
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: nival interactive

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:08 UTCUpdated Record last modified

nival interactive etherlords DOWNGRADE

Affected: 1.0 · 1.0_1 · 1.0_2 · 1.0_3 · 1.0_4 · 1.0_5 · 1.0_6 · 1.0_7

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0

1. Check installed version

apt-cache policy etherlords || rpm -q etherlords || etherlords --version

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

apt-cache madison etherlords sudo apt install etherlords=<VERSION_BEFORE_1.0> sudo apt-mark hold etherlords

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

dnf --showduplicates list etherlords sudo dnf downgrade etherlords-<VERSION_BEFORE_1.0> sudo dnf versionlock add etherlords

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.

nival interactive etherlords ii DOWNGRADE

Affected: 1.0 · 1.0_1 · 1.0_2 · 1.0_3

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0

1. Check installed version

apt-cache policy etherlords-ii || rpm -q etherlords-ii || etherlords-ii --version

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

apt-cache madison etherlords-ii sudo apt install etherlords-ii=<VERSION_BEFORE_1.0> sudo apt-mark hold etherlords-ii

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

dnf --showduplicates list etherlords-ii sudo dnf downgrade etherlords-ii-<VERSION_BEFORE_1.0> sudo dnf versionlock add etherlords-ii

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.

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-1869?

etherlords: downgrade or apply the listed mitigation; etherlords ii: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2004-1869 being exploited?

CVE-2004-1869 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-1869 affect?

CVE-2004-1869 affects etherlords, etherlords ii. Severity is medium (CVSS 5.0). Etherlords I 1.07 and earlier and Etherlords II 1.03 and earlier allows remote attackers to cause a denial of service (crash) by sending a packet that specifies the size for the next packet, then sending a larger packet than specified, whic

How urgent is CVE-2004-1869?

Priority 42/100. Public exploit reference

References

← Back to latest CVEs