CVE-2008-1447

CRITICALNVD 6.89.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 95% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs). NVD baseline CVSS 6.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: epss, ghsa, nvd
Weaponized
9.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 95%
  • Public exploit code is available (Metasploit, Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 95%CVSS: 6.8Exploit: Metasploit · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed services: Not assessed

A fix is available — apply it.

The DNS protocol, as implemented in (1) BIND 8 and 9 before 9.5.0-P1, 9.4.2-P1, and 9.3.5-P1; (2) Microsoft DNS in Windows 2000 SP4, XP SP2 and SP3, and Server 2003 SP1 and SP2; and other implementations allow remote attackers to spoof DNS traffic via a birthday attack that uses in-bailiwick referrals to conduct cache poisoning against recursive resolvers, related to insufficient randomness of DNS transaction IDs and source ports, aka "DNS Insufficient Socket Entropy Vulnerability" or "the Kaminsky bug."

CVSS v3
6.8
EG Score
9.0CRITICALhigh confidence
EG Risk
83
EG Risk 83/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
Severity90% × 45%
Exploitation95% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
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
95%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; 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 public PoC (EG-KEV: weaponized) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). 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

July 8, 2008

Last Modified

April 23, 2026

Advisory Details (2)

Auto-updated May 30, 2026
Patch available.
genericMentions a patch (unverified)

#494401 - ruby1.8: New release (1.8.7-p71) with vulnerabilities fixes - Debian Bug report logs

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494401
generic

Invisible Denizen: Kaminsky's DNS Issue Accidentally Leaked?

http://blog.invisibledenizen.org/2008/07/kaminskys-dns-issue-accidentally-leaked.html

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibdns35 (1:9.4.2-10ubuntu0.1) @ hardy2026-05-30ubuntu
ubuntudnsmasq-base (2.41-2ubuntu2.1) @ hardy2026-05-30ubuntu
redhatdnsmasq-0:2.45-1.el5_2.12008-08-11redhat
redhatselinux-policy-0:2.4.6-137.1.el5_22008-07-08redhat

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

(33 across 6 ecosystems)
Debian:11(7)
PackageVulnerable rangeFix by version rangeDependents
adns—
  • every version up to 1.4-2: fixed in 1.4-2
—
bind9—
  • every version up to 1:9.5.0.dfsg-5: fixed in 1:9.5.0.dfsg-5
—
dnsmasq—
  • every version up to 2.43-1: fixed in 2.43-1
—
dnspython—
  • every version up to 1.7.1-1: fixed in 1.7.1-1
—
libnet-dns-perl—
  • every version up to 0.63-2: fixed in 0.63-2
—
refpolicy—
  • every version up to 2:0.0.20080702-1: fixed in 2:0.0.20080702-1
—
udns—
  • every version up to 0.2-1: fixed in 0.2-1
—
Debian:12(7)
PackageVulnerable rangeFix by version rangeDependents
adns—
  • every version up to 1.4-2: fixed in 1.4-2
—
bind9—
  • every version up to 1:9.5.0.dfsg-5: fixed in 1:9.5.0.dfsg-5
—
dnsmasq—
  • every version up to 2.43-1: fixed in 2.43-1
—
dnspython—
  • every version up to 1.7.1-1: fixed in 1.7.1-1
—
libnet-dns-perl—
  • every version up to 0.63-2: fixed in 0.63-2
—
refpolicy—
  • every version up to 2:0.0.20080702-1: fixed in 2:0.0.20080702-1
—
udns—
  • every version up to 0.2-1: fixed in 0.2-1
—
Debian:13(7)
PackageVulnerable rangeFix by version rangeDependents
adns—
  • every version up to 1.4-2: fixed in 1.4-2
—
bind9—
  • every version up to 1:9.5.0.dfsg-5: fixed in 1:9.5.0.dfsg-5
—
dnsmasq—
  • every version up to 2.43-1: fixed in 2.43-1
—
dnspython—
  • every version up to 1.7.1-1: fixed in 1.7.1-1
—
libnet-dns-perl—
  • every version up to 0.63-2: fixed in 0.63-2
—
refpolicy—
  • every version up to 2:0.0.20080702-1: fixed in 2:0.0.20080702-1
—
udns—
  • every version up to 0.2-1: fixed in 0.2-1
—
Debian:14(7)
PackageVulnerable rangeFix by version rangeDependents
adns—
  • every version up to 1.4-2: fixed in 1.4-2
—
bind9—
  • every version up to 1:9.5.0.dfsg-5: fixed in 1:9.5.0.dfsg-5
—
dnsmasq—
  • every version up to 2.43-1: fixed in 2.43-1
—
dnspython—
  • every version up to 1.7.1-1: fixed in 1.7.1-1
—
libnet-dns-perl—
  • every version up to 0.63-2: fixed in 0.63-2
—
refpolicy—
  • every version up to 2:0.0.20080702-1: fixed in 2:0.0.20080702-1
—
udns—
  • every version up to 0.2-1: fixed in 0.2-1
—
Debian:4.0(4)
PackageVulnerable rangeFix by version rangeDependents
bind91:9.3.4-2, 1:9.3.4-2etch1, 1:9.3.4-2etch2~bpo.1
  • every version up to 1:9.3.4-2etch3: fixed in 1:9.3.4-2etch3
—
dnsmasq2.35-1
  • every version up to 2.35-1+etch4: fixed in 2.35-1+etch4
—
python-dns2.3.0-5.1
  • every version up to 2.3.0-5.2+etch1: fixed in 2.3.0-5.2+etch1
—
refpolicy0.0.20061018-5
  • every version up to 0.0.20061018-5.1+etch1: fixed in 0.0.20061018-5.1+etch1
—
Debian:5.0(1)
PackageVulnerable rangeFix by version rangeDependents
bind9—
  • every version up to 1:9.4.2-10+lenny1: fixed in 1:9.4.2-10+lenny1
—

Weakness Classification(1)

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

All Vendor Advisories

(4)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

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-06 15:09 UTCEPSS rescore
  2. 2026-10-04 02:14 UTCOSV refresh
  3. 2026-09-29 07:48 UTCEG score recompute
  4. 2026-09-17 19:20 UTCEPSS rescore
  5. 2026-09-14 16:14 UTCOSV refresh
  6. 2026-09-12 14:54 UTCEPSS rescore
  7. 2026-09-10 09:24 UTCEPSS rescore
  8. 2026-09-06 13:41 UTCEPSS rescore
  9. 2026-09-05 15:22 UTCEPSS rescore
  10. 2026-08-28 21:34 UTCEPSS rescore
  11. 2026-08-26 16:13 UTCOSV refresh
  12. 2026-08-15 01:24 UTCEPSS rescore
  13. 2026-08-10 06:10 UTCOSV refresh
  14. 2026-08-07 16:21 UTCEPSS rescore
  15. 2026-07-25 14:12 UTCEPSS rescore
  16. 2026-07-25 06:41 UTCOSV refresh
  17. 2026-07-24 14:12 UTCEPSS rescore
  18. 2026-07-23 14:14 UTCEPSS rescore
  19. 2026-07-23 00:55 UTCEG score recompute
  20. 2026-07-23 00:34 UTCEG score recompute
  21. 2026-07-23 00:00 UTCEG score recompute
  22. 2026-07-22 21:39 UTCEG score recompute
  23. 2026-07-13 22:25 UTCEPSS rescore
  24. 2026-07-13 06:07 UTCEPSS rescore
  25. 2026-07-11 08:22 UTCEPSS rescore
Show 46 more
  1. 2026-07-11 08:22 UTCEPSS rescore
  2. 2026-07-09 19:04 UTCEPSS rescore
  3. 2026-07-08 01:35 UTCOSV refresh
  4. 2026-07-01 15:02 UTCEPSS rescore
  5. 2026-07-01 15:02 UTCEPSS rescore
  6. 2026-06-30 23:19 UTCEPSS rescore
  7. 2026-06-29 14:02 UTCEPSS rescore
  8. 2026-06-29 14:02 UTCEPSS rescore
  9. 2026-06-28 14:03 UTCEPSS rescore
  10. 2026-06-28 04:52 UTCEPSS rescore
  11. 2026-06-23 21:29 UTCEPSS rescore
  12. 2026-06-23 21:29 UTCEPSS rescore
  13. 2026-06-19 13:25 UTCOSV refresh
  14. 2026-06-17 17:49 UTCEPSS rescore
  15. 2026-06-17 17:49 UTCEPSS rescore
  16. 2026-06-15 17:44 UTCEPSS rescore
  17. 2026-06-14 23:13 UTCEPSS rescore
  18. 2026-06-12 23:08 UTCEPSS rescore
  19. 2026-06-12 23:08 UTCEPSS rescore
  20. 2026-06-10 22:14 UTCEPSS rescore
  21. 2026-06-10 13:17 UTCEPSS rescore
  22. 2026-06-08 14:13 UTCEPSS rescore
  23. 2026-06-07 15:22 UTCEPSS rescore
  24. 2026-06-05 22:44 UTCEPSS rescore
  25. 2026-06-05 22:44 UTCEPSS rescore
  26. 2026-06-05 06:07 UTCEPSS rescore
  27. 2026-06-04 13:09 UTCEPSS rescore
  28. 2026-06-04 13:09 UTCEPSS rescore
  29. 2026-06-01 13:49 UTCEPSS rescore
  30. 2026-06-01 13:49 UTCEPSS rescore
  31. 2026-06-01 13:49 UTCEPSS rescore
  32. 2026-05-31 22:28 UTCEPSS rescore
  33. 2026-05-31 22:28 UTCEPSS rescore
  34. 2026-05-30 21:08 UTCEG score recompute
  35. 2026-05-30 21:08 UTCVendor advisory
  36. 2026-05-30 21:08 UTCGHSA enrichment
  37. 2026-05-29 13:40 UTCEPSS rescore
  38. 2026-05-28 13:42 UTCEPSS rescore
  39. 2026-05-28 13:42 UTCEPSS rescore
  40. 2026-05-28 13:42 UTCEPSS rescore
  41. 2026-05-27 13:38 UTCEPSS rescore
  42. 2026-05-27 13:37 UTCEPSS rescore
  43. 2026-05-26 07:16 UTCEPSS rescore
  44. 2026-05-26 07:16 UTCEPSS rescore
  45. 2026-05-22 17:43 UTCOSV refresh
  46. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(5 references)

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

  • Exploit-DBEDB-6130✓ verified
    First seen Jul 25, 2008

    BIND 9.x - Remote DNS Cache Poisoning

    Open source ↗
  • Exploit-DBEDB-6123✓ verified
    First seen Jul 24, 2008

    BIND 9.x - Remote DNS Cache Poisoning

    Open source ↗
  • Exploit-DBEDB-6122✓ verified
    First seen Jul 23, 2008

    BIND 9.4.1 < 9.4.2 - Remote DNS Cache Poisoning (Metasploit)

    Open source ↗
  • Metasploitauxiliary/spoof/dns/bailiwicked_domain✓ verified
    First seen Jul 21, 2008

    DNS BailiWicked Domain Attack

    Open source ↗
  • Metasploitauxiliary/spoof/dns/bailiwicked_host✓ verified
    First seen Jul 21, 2008

    DNS BailiWicked Host Attack

    Open source ↗

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2008-1447?
CVE-2008-1447 is a critical vulnerability published on July 8, 2008. The DNS protocol, as implemented in (1) BIND 8 and 9 before 9.5.0-P1, 9.4.2-P1, and 9.3.5-P1; (2) Microsoft DNS in Windows 2000 SP4, XP SP2 and SP3, and Server 2003 SP1 and SP2; and other implementations allow remote attackers to spoof DNS traffic via a birthday attack that uses in-bailiwick…
When was CVE-2008-1447 disclosed?
CVE-2008-1447 was first published on July 8, 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-1447 actively exploited?
CVE-2008-1447 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 95% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2008-1447?
CVE-2008-1447 has a CVSS v3 base score of 6.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
How do I remediate CVE-2008-1447?
A fix for CVE-2008-1447 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-2008-1447

Explore →

Is Your Infrastructure Affected by CVE-2008-1447?

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

Book a Demo →Browse All CVEs