CVE-2004-2687

HIGHCVSS v2 · 9.39.3—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 9.3 — v2 rates that HIGH (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:M/Au:N/C:C/I:C/A:C. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 88.2% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: epss, nvd_v2
Weaponized
9.3EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 88%
  • Public exploit code is available (Metasploit, Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 88%CVSS v2: 9.3Exploit: Metasploit · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed services: Not assessed

A fix is available — apply it.

distcc 2.x, as used in XCode 1.5 and others, when not configured to restrict access to the server port, allows remote attackers to execute arbitrary commands via compilation jobs, which are executed by the server without authorization checks.

CVSS v2.0 (legacy)
9.3HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
9.3HIGHlow confidence
EG Risk
82
EG Risk 82/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity93% × 45%
Exploitation88% × 40%
Automatability30% × 15%
CISA SSVC: Track at low, Track or Track* at medium and Track* or Attend at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
88%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at low, Track or Track* at medium and Track* or Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (EG-KEV: weaponized) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

December 31, 2004

Last Modified

June 16, 2026

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
distcc—
  • every version up to 2.18.1-1: fixed in 2.18.1-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
distcc—
  • every version up to 2.18.1-1: fixed in 2.18.1-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
distcc—
  • every version up to 2.18.1-1: fixed in 2.18.1-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
distcc—
  • every version up to 2.18.1-1: fixed in 2.18.1-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 2× in last 7d / 7× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-09 19:58 UTCEPSS rescore
  2. 2026-10-05 16:51 UTCOSV refresh
  3. 2026-09-29 02:42 UTCEG score recompute
  4. 2026-09-18 19:20 UTCEPSS rescore
  5. 2026-09-17 19:20 UTCEPSS rescore
  6. 2026-09-17 19:20 UTCEPSS rescore
  7. 2026-09-16 00:54 UTCOSV refresh
  8. 2026-09-10 09:23 UTCEPSS rescore
  9. 2026-08-27 23:21 UTCOSV refresh
  10. 2026-08-11 13:12 UTCOSV refresh
  11. 2026-08-08 16:30 UTCEPSS rescore
  12. 2026-07-26 13:25 UTCEG score recompute▲ 9.30
  13. 2026-07-26 12:39 UTCOSV refresh
  14. 2026-07-24 14:11 UTCEPSS rescore
  15. 2026-07-23 00:47 UTCEG score recompute
  16. 2026-07-23 00:27 UTCEG score recompute▼ 8.30
  17. 2026-07-22 23:51 UTCEG score recompute▲ 8.30
  18. 2026-07-22 21:31 UTCEG score recompute▼ 9.00
  19. 2026-07-15 16:53 UTCEPSS rescore
  20. 2026-07-13 22:24 UTCEPSS rescore
  21. 2026-07-09 07:15 UTCOSV refresh
  22. 2026-07-06 02:19 UTCEPSS rescore
  23. 2026-07-06 02:19 UTCEPSS rescore
  24. 2026-07-01 15:01 UTCEPSS rescore
  25. 2026-06-28 04:52 UTCEPSS rescore
Show 30 more
  1. 2026-06-25 13:46 UTCEPSS rescore
  2. 2026-06-24 14:01 UTCEPSS rescore
  3. 2026-06-23 21:29 UTCEPSS rescore
  4. 2026-06-21 01:56 UTCEPSS rescore
  5. 2026-06-20 19:42 UTCOSV refresh
  6. 2026-06-18 17:49 UTCEPSS rescore
  7. 2026-06-18 17:49 UTCEPSS rescore
  8. 2026-06-16 17:49 UTCEPSS rescore
  9. 2026-06-16 17:49 UTCEPSS rescore
  10. 2026-06-15 17:44 UTCEPSS rescore
  11. 2026-06-14 23:13 UTCEPSS rescore
  12. 2026-06-14 23:13 UTCEPSS rescore
  13. 2026-06-12 23:08 UTCEPSS rescore
  14. 2026-06-10 22:14 UTCEPSS rescore
  15. 2026-06-07 15:21 UTCEPSS rescore
  16. 2026-06-05 22:43 UTCEPSS rescore
  17. 2026-06-05 22:43 UTCEPSS rescore
  18. 2026-06-04 13:09 UTCEPSS rescore
  19. 2026-06-04 13:09 UTCEPSS rescore
  20. 2026-05-31 14:47 UTCEG score recompute
  21. 2026-05-31 14:47 UTCGHSA enrichment
  22. 2026-05-29 13:40 UTCEPSS rescore
  23. 2026-05-29 13:40 UTCEPSS rescore
  24. 2026-05-22 21:15 UTCEPSS rescore
  25. 2026-05-22 20:43 UTCOSV refresh
  26. 2026-05-20 22:36 UTCEPSS rescore
  27. 2026-05-20 22:36 UTCEPSS rescore
  28. 2026-05-20 11:20 UTCEPSS rescore
  29. 2026-05-20 11:20 UTCEPSS rescore
  30. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(4 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 1 Exploit-DB entry, 1 GitHub PoC), as is 1 Nuclei detection template. A detection template checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • Metasploitexploit/unix/misc/distcc_exec✓ verified
    Published Jun 16, 2006

    DistCC Daemon Command Execution

    Open source ↗
  • Exploit-DBEDB-9915✓ verified
    Published Feb 1, 2002

    DistCC Daemon - Command Execution (Metasploit)

    Open source ↗
  • Nucleinetwork/cves/2004/CVE-2004-2687.yaml
    Published Aug 16, 2024

    Distccd v1 - Remote Code Execution

    Open source ↗
  • GitHub PoCh3x0v3rl0rd/distccd_rce_CVE-2004-2687
    Published Jul 1, 2021
    Open source ↗

Frequently asked(4)

What is CVE-2004-2687?
CVE-2004-2687 is a high vulnerability published on December 31, 2004. distcc 2.x, as used in XCode 1.5 and others, when not configured to restrict access to the server port, allows remote attackers to execute arbitrary commands via compilation jobs, which are executed by the server without authorization checks.
When was CVE-2004-2687 disclosed?
CVE-2004-2687 was first published on December 31, 2004, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2004-2687 actively exploited?
CVE-2004-2687 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 88% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
How do I remediate CVE-2004-2687?
A fix for CVE-2004-2687 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2004-2687

Explore →

Is Your Infrastructure Affected by CVE-2004-2687?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.