CVE-2008-3905

NONECVSS 0.0
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 2%CVSS: Exploit: NoneExposed: 0

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 v3
EG Score
0.0(none)
EPSS
82.2%
KEV
Not listed

Published

September 4, 2008

Last Modified

April 23, 2026

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.

Frequently asked(4)

What is CVE-2008-3905?
CVE-2008-3905 is a none vulnerability 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 disclosed?
CVE-2008-3905 was first published in the National Vulnerability Database on September 4, 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-3905 actively exploited?
CVE-2008-3905 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 82.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2008-3905?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2008-3905, 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-3905

Explore →

Is Your Infrastructure Affected by CVE-2008-3905?

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