CVE-2008-3905

MEDIUMCVSS v2 · 5.85.8—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 5.8 — v2 rates that MEDIUM (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:N/I:P/A:P. 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 2.4% 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
5.8EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 2.4%CVSS v2: 5.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

resolv.rb in Ruby 1.8.5 and earlier, 1.8.6 before 1.8.6-p287, 1.8.7 before 1.8.7-p72, and 1.9 r18423 and earlier uses sequential transaction IDs and constant source ports for DNS requests, which makes it easier for remote attackers to spoof DNS responses, a different vulnerability than CVE-2008-1447.

CVSS v2.0 (legacy)
5.8MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
5.8MEDIUMlow confidence
EG Risk
32
EG Risk 32/100

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 (value × EchelonGraph’s weight)
Severity58% × 45%
The EG Score, 5.8 of 10.
Exploitation2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability30% × 15%
EchelonGraph's default before algorithm v3.4: CISA had not published Automatable for this CVE.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).
Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
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
2.4%
EPSS %ILE
83rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).

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

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

Published

September 4, 2008

Last Modified

April 23, 2026

References (24)

15 of 24 shown · show the other 9

Vendor Advisories for CVE-2008-3905(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibruby1.8 (1.8.6.111-2ubuntu1.2) @ hardy2026-05-30ubuntu
redhatruby4-0-main-4.0.0-33.3.hum12026-04-17redhat
redhatruby3-3-main-3.3.10-23.1.hum12026-04-09redhat
redhatruby3-4-main-3.4.8-31.1.hum12026-04-09redhat
redhatruby-0:1.6.8-13.el32008-10-21redhat
redhatruby-0:1.8.5-5.el5_2.52008-10-21redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 1 ecosystem)
Debian:4.0(2)
PackageVulnerable rangeFix by version rangeDependents
ruby1.81.8.5-4, 1.8.5-4etch1, 1.8.5-4etch2
  • every version up to 1.8.5-4etch3: fixed in 1.8.5-4etch3
—
ruby1.91.9.0+20060609-1, 1.9.0+20060609-1etch1, 1.9.0+20060609-1etch2
  • every version up to 1.9.0+20060609-1etch3: fixed in 1.9.0+20060609-1etch3
—

Weakness Classification(1)

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

Additional Vendor Advisories

(3)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 17× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 82 of 113 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 18 repeat rows among the latest 100 are merged into the row they repeat. The 31 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 13:38 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  2. 2026-10-10 19:53 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  3. 2026-10-09 20:00 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  4. 2026-10-08 16:33 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  5. 2026-10-07 23:37 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  6. 2026-10-06 15:09 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  7. 2026-10-05 17:37 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  8. 2026-10-04 23:15 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  9. 2026-10-03 14:20 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  10. 2026-10-01 19:42 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  11. 2026-09-30 14:57 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  12. 2026-09-29 07:51 UTCEG score recompute
  13. 2026-09-26 15:52 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  14. 2026-09-18 19:20 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  15. 2026-09-17 19:20 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  16. 2026-09-15 03:04 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  17. 2026-09-12 14:54 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  18. 2026-09-10 09:24 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  19. 2026-09-06 13:41 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  20. 2026-09-05 15:22 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  21. 2026-09-04 13:55 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  22. 2026-09-04 04:59 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
  23. 2026-08-30 01:14 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  24. 2026-08-28 21:34 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  25. 2026-08-15 01:24 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
Show 57 more
  1. 2026-08-08 16:31 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  2. 2026-08-07 16:21 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  3. 2026-08-06 13:41 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  4. 2026-08-05 19:11 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  5. 2026-08-04 15:03 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  6. 2026-08-03 10:28 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  7. 2026-07-30 01:25 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  8. 2026-07-26 13:36 UTCEG score recompute▲ 5.80
  9. 2026-07-25 14:12 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  10. 2026-07-24 14:12 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  11. 2026-07-23 14:14 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  12. 2026-07-23 00:56 UTCEG score recompute
  13. 2026-07-23 00:35 UTCEG score recompute
  14. 2026-07-23 00:01 UTCEG score recompute
  15. 2026-07-22 21:40 UTCEG score recompute
  16. 2026-07-20 17:03 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  17. 2026-07-18 09:59 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  18. 2026-07-16 16:58 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  19. 2026-07-15 16:54 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  20. 2026-07-15 01:55 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  21. 2026-07-13 22:25 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  22. 2026-07-13 06:07 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  23. 2026-07-11 08:22 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  24. 2026-07-09 19:04 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  25. 2026-07-08 15:09 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  26. 2026-07-06 16:23 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  27. 2026-07-06 02:19 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  28. 2026-07-05 02:26 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  29. 2026-07-04 06:27 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  30. 2026-07-02 14:00 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  31. 2026-07-01 15:02 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  32. 2026-06-30 23:19 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  33. 2026-06-29 14:02 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  34. 2026-06-28 14:03 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  35. 2026-06-28 04:52 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  36. 2026-06-27 03:04 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  37. 2026-06-25 13:46 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  38. 2026-06-24 14:02 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  39. 2026-06-23 21:29 UTCEPSS rescoreEPSS 2.4% · 81st percentile
  40. 2026-06-22 14:22 UTCEPSS rescoreEPSS 2.4% · 81st percentile
  41. 2026-06-21 14:53 UTCEPSS rescoreEPSS 2.4% · 81st percentile
  42. 2026-06-21 01:56 UTCEPSS rescoreEPSS 2.4% · 81st percentile
  43. 2026-06-19 19:22 UTCEPSS rescoreEPSS 2.4% · 81st percentile
  44. 2026-06-18 17:49 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  45. 2026-06-17 17:49 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  46. 2026-06-16 17:49 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  47. 2026-06-15 17:44 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
  48. 2026-06-14 23:13 UTCEPSS rescoreEPSS 3.2% · 87th percentile
  49. 2026-06-13 22:57 UTCEPSS rescoreEPSS 3.2% · 87th percentile
  50. 2026-06-12 23:08 UTCEPSS rescoreEPSS 3.2% · 87th percentile
  51. 2026-06-11 13:56 UTCEPSS rescoreEPSS 3.2% · 87th percentile
  52. 2026-06-10 22:14 UTCEPSS rescoreEPSS 3.2% · 87th percentile
  53. 2026-06-10 13:17 UTCEPSS rescoreEPSS 3.2% · 87th percentile
  54. 2026-06-08 14:13 UTCEPSS rescoreEPSS 3.2% · 87th percentile
  55. 2026-06-07 15:22 UTCEPSS rescoreEPSS 3.2% · 87th percentile
  56. 2026-06-06 13:44 UTCEPSS rescoreEPSS 3.2% · 87th percentile
  57. 2026-06-05 22:44 UTCEPSS rescoreEPSS 3.2% · 87th percentile

Related CVEs(same product + same vendor + same CWE)

Frequently asked(4)

What is CVE-2008-3905?
CVE-2008-3905 is a medium-severity vulnerability; its CVE record was published on September 4, 2008. resolv.rb in Ruby 1.8.5 and earlier, 1.8.6 before 1.8.6-p287, 1.8.7 before 1.8.7-p72, and 1.9 r18423 and earlier uses sequential transaction IDs and constant source ports for DNS requests, which makes it easier for remote attackers to spoof DNS responses, a different vulnerability than…
When was CVE-2008-3905 made public?
CVE-2008-3905 was made public on September 3, 2008: that is the date its CVE record's CNA, MITRE Corporation, gives for when the vulnerability was made public. The CVE record itself was published on September 4, 2008. EchelonGraph's copy of the record carries a last-modified date of April 23, 2026; the record at its source may have been updated since.
Is CVE-2008-3905 actively exploited?
CVE-2008-3905 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.4% probability of exploitation in the next 30 days (83rd percentile of EPSS-scored CVEs).
How do I remediate CVE-2008-3905?
A fix for CVE-2008-3905 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2008-3905 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2008-3905

Explore →

Is Your Infrastructure Affected by CVE-2008-3905?

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

Book a Demo →Browse All CVEs