CVE-2004-0601: distcc before 2.16, when running on 64-bit platforms, does not interpret IP-based access control rules correct

This month

HIGH 7.5DOWNGRADE

CVE-2004-0601 is a high-severity flaw (CVSS 7.5) affecting distcc. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

distcc before 2.16, when running on 64-bit platforms, does not interpret IP-based access control rules correctly, which could allow remote attackers to bypass intended restrictions.

Why this priority

High severity

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

Risk facts

CVSS score	7.5 (High)
EPSS exploit chance	1.6% (top 24%)
CISA exploited list	No
Published	2004-12-23
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: distcc

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

Am I affected?

Timeline

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

distcc distcc DOWNGRADE

Affected: 2.7 · 2.9 · 2.10 · 2.11 · 2.12 · 2.13 · 2.14 · 2.15

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.7

1. Check installed version

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

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

apt-cache madison distcc sudo apt install distcc=<VERSION_BEFORE_2.7> sudo apt-mark hold distcc

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

dnf --showduplicates list distcc sudo dnf downgrade distcc-<VERSION_BEFORE_2.7> sudo dnf versionlock add distcc

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

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

Is CVE-2004-0601 being exploited?

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

CVE-2004-0601 affects distcc. Severity is high (CVSS 7.5). distcc before 2.16, when running on 64-bit platforms, does not interpret IP-based access control rules correctly, which could allow remote attackers to bypass intended restrictions.

How urgent is CVE-2004-0601?

Priority 45/100. High severity

References

← Back to latest CVEs