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.

Sources: epss, nvd_v2
Trending — 3 sources updated this weekWeaponized
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: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.3(low)
EG Risk
82(Track)
EG Risk 82/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
88%
EPSS %ILE
100%
KEV
Not listed

Published

December 31, 2004

Last Modified

June 16, 2026

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 14× 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-07-26 13:25 UTCEG score recompute 9.30
  2. 2026-07-26 12:39 UTCOSV refresh
  3. 2026-07-24 14:11 UTCEPSS rescore
  4. 2026-07-23 00:47 UTCEG score recompute
  5. 2026-07-23 00:27 UTCEG score recompute 8.30
  6. 2026-07-22 23:51 UTCEG score recompute 8.30
  7. 2026-07-22 21:31 UTCEG score recompute 9.00
  8. 2026-07-15 16:53 UTCEPSS rescore
  9. 2026-07-13 22:24 UTCEPSS rescore
  10. 2026-07-09 07:15 UTCOSV refresh
  11. 2026-07-06 02:19 UTCEPSS rescore
  12. 2026-07-06 02:19 UTCEPSS rescore
  13. 2026-07-01 15:01 UTCEPSS rescore
  14. 2026-06-28 04:52 UTCEPSS rescore
  15. 2026-06-25 13:46 UTCEPSS rescore
  16. 2026-06-24 14:01 UTCEPSS rescore
  17. 2026-06-23 21:29 UTCEPSS rescore
  18. 2026-06-21 01:56 UTCEPSS rescore
  19. 2026-06-20 19:42 UTCOSV refresh
  20. 2026-06-18 17:49 UTCEPSS rescore
  21. 2026-06-18 17:49 UTCEPSS rescore
  22. 2026-06-16 17:49 UTCEPSS rescore
  23. 2026-06-16 17:49 UTCEPSS rescore
  24. 2026-06-15 17:44 UTCEPSS rescore
  25. 2026-06-14 23:13 UTCEPSS rescore
Show 19 more
  1. 2026-06-14 23:13 UTCEPSS rescore
  2. 2026-06-12 23:08 UTCEPSS rescore
  3. 2026-06-10 22:14 UTCEPSS rescore
  4. 2026-06-07 15:21 UTCEPSS rescore
  5. 2026-06-05 22:43 UTCEPSS rescore
  6. 2026-06-05 22:43 UTCEPSS rescore
  7. 2026-06-04 13:09 UTCEPSS rescore
  8. 2026-06-04 13:09 UTCEPSS rescore
  9. 2026-05-31 14:47 UTCEG score recompute
  10. 2026-05-31 14:47 UTCGHSA enrichment
  11. 2026-05-29 13:40 UTCEPSS rescore
  12. 2026-05-29 13:40 UTCEPSS rescore
  13. 2026-05-22 21:15 UTCEPSS rescore
  14. 2026-05-22 20:43 UTCOSV refresh
  15. 2026-05-20 22:36 UTCEPSS rescore
  16. 2026-05-20 22:36 UTCEPSS rescore
  17. 2026-05-20 11:20 UTCEPSS rescore
  18. 2026-05-20 11:20 UTCEPSS rescore
  19. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(4 references)

Working exploit code is in the public domain (1 Metasploit module) (1 GitHub PoC) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCh3x0v3rl0rd/distccd_rce_CVE-2004-2687
    First seen Jul 1, 2021
    Open source ↗
  • Nucleinetwork/cves/2004/CVE-2004-2687.yaml
    First seen Jan 1, 2004

    Distccd v1 - Remote Code Execution

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

    DistCC Daemon - Command Execution (Metasploit)

    Open source ↗
  • Metasploitexploit/unix/misc/distcc_exec✓ verified
    First seen Feb 1, 2002

    DistCC Daemon Command Execution

    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 in the National Vulnerability Database 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. FIRST EPSS estimates a 88% probability of exploitation in the next 30 days, which ranks it in the top 0.2% of all scored CVEs.
How do I remediate CVE-2004-2687?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2004-2687, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for 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.