CVE-2008-2639

HIGHCVSS v2 · 7.67.6—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 7.6 — 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:H/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 77.7% 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
Weaponized
7.6EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 78%
  • Public exploit code is available (Metasploit, Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 78%CVSS v2: 7.6Exploit: 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.

Stack-based buffer overflow in the ODBC server service in Citect CitectSCADA 6 and 7, and CitectFacilities 7, allows remote attackers to execute arbitrary code via a long string in the second application packet in a TCP session on port 20222.

CVSS v2.0 (legacy)
7.6HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
7.6(low)
EG Risk
70(Track)
EG Risk 70/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
Severity76% × 45%
Exploitation78% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
78%
EPSS %ILE
100%
KEV
Not listed

Published

June 16, 2008

Last Modified

April 23, 2026

References (24)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 0× in last 7d / 4× 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-08-15 01:24 UTCEPSS rescore
  2. 2026-08-07 16:21 UTCEPSS rescore
  3. 2026-08-05 19:11 UTCEPSS rescore
  4. 2026-08-03 10:28 UTCEPSS rescore
  5. 2026-07-26 13:35 UTCEG score recompute▲ 7.60
  6. 2026-07-24 14:12 UTCEPSS rescore
  7. 2026-07-23 14:14 UTCEPSS rescore
  8. 2026-07-23 00:56 UTCEG score recompute
  9. 2026-07-23 00:34 UTCEG score recompute▼ 7.80
  10. 2026-07-23 00:01 UTCEG score recompute▲ 7.80
  11. 2026-07-22 21:40 UTCEG score recompute▼ 9.00
  12. 2026-07-20 17:03 UTCEPSS rescore
  13. 2026-07-15 16:54 UTCEPSS rescore
  14. 2026-07-15 16:54 UTCEPSS rescore
  15. 2026-07-13 22:25 UTCEPSS rescore
  16. 2026-07-11 08:22 UTCEPSS rescore
  17. 2026-07-11 08:22 UTCEPSS rescore
  18. 2026-07-09 19:04 UTCEPSS rescore
  19. 2026-07-04 06:27 UTCEPSS rescore
  20. 2026-07-01 15:02 UTCEPSS rescore
  21. 2026-07-01 15:02 UTCEPSS rescore
  22. 2026-06-27 03:04 UTCEPSS rescore
  23. 2026-06-25 13:46 UTCEPSS rescore
  24. 2026-06-25 13:46 UTCEPSS rescore
  25. 2026-06-24 14:02 UTCEPSS rescore
Show 33 more
  1. 2026-06-24 14:02 UTCEPSS rescore
  2. 2026-06-23 21:29 UTCEPSS rescore
  3. 2026-06-23 21:29 UTCEPSS rescore
  4. 2026-06-21 14:53 UTCEPSS rescore
  5. 2026-06-21 14:53 UTCEPSS rescore
  6. 2026-06-21 01:56 UTCEPSS rescore
  7. 2026-06-21 01:56 UTCEPSS rescore
  8. 2026-06-18 17:49 UTCEPSS rescore
  9. 2026-06-18 17:49 UTCEPSS rescore
  10. 2026-06-16 17:49 UTCEPSS rescore
  11. 2026-06-16 17:49 UTCEPSS rescore
  12. 2026-06-15 17:44 UTCEPSS rescore
  13. 2026-06-14 23:13 UTCEPSS rescore
  14. 2026-06-13 22:57 UTCEPSS rescore
  15. 2026-06-12 23:08 UTCEPSS rescore
  16. 2026-06-12 23:08 UTCEPSS rescore
  17. 2026-06-10 13:17 UTCEPSS rescore
  18. 2026-06-05 22:44 UTCEPSS rescore
  19. 2026-06-05 22:44 UTCEPSS rescore
  20. 2026-05-31 00:13 UTCEPSS rescore
  21. 2026-05-31 00:13 UTCEPSS rescore
  22. 2026-05-30 21:26 UTCEG score recompute
  23. 2026-05-30 21:26 UTCGHSA enrichment
  24. 2026-05-28 13:42 UTCEPSS rescore
  25. 2026-05-28 13:42 UTCEPSS rescore
  26. 2026-05-28 13:42 UTCEPSS rescore
  27. 2026-05-26 13:41 UTCEPSS rescore
  28. 2026-05-26 13:41 UTCEPSS rescore
  29. 2026-05-22 21:15 UTCEPSS rescore
  30. 2026-05-22 21:15 UTCEPSS rescore
  31. 2026-05-20 22:37 UTCEPSS rescore
  32. 2026-05-20 22:36 UTCEPSS rescore
  33. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(3 references)

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

  • Exploit-DBEDB-16380✓ verified
    First seen Nov 14, 2010

    CitectSCADA/CitectFacilities ODBC - Remote Buffer Overflow (Metasploit)

    Open source ↗
  • Exploit-DBEDB-6387✓ verified
    First seen Sep 5, 2008

    CitectSCADA ODBC Server - Remote Stack Buffer Overflow (Metasploit)

    Open source ↗
  • Metasploitexploit/windows/scada/citect_scada_odbc✓ verified
    First seen Jun 11, 2008

    CitectSCADA/CitectFacilities ODBC Buffer Overflow

    Open source ↗

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2008-2639?
CVE-2008-2639 is a high vulnerability published on June 16, 2008. Stack-based buffer overflow in the ODBC server service in Citect CitectSCADA 6 and 7, and CitectFacilities 7, allows remote attackers to execute arbitrary code via a long string in the second application packet in a TCP session on port 20222.
When was CVE-2008-2639 disclosed?
CVE-2008-2639 was first published in the National Vulnerability Database on June 16, 2008, with the most recent update on April 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2008-2639 actively exploited?
CVE-2008-2639 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 78% probability of exploitation in the next 30 days, which ranks it in the top 0.5% of all scored CVEs.
How do I remediate CVE-2008-2639?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2008-2639, 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-2008-2639

Explore →

Is Your Infrastructure Affected by CVE-2008-2639?

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

Start Free Scan →Browse All CVEs