CVE-2008-1447

MEDIUMNVD 6.89.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 87% probability of exploitation within the next 30 days (top 0.6% of all CVEs). NVD baseline CVSS 6.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Weaponized
6.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 95%
CISA-KEV: Not listedEPSS: 95%CVSS: 6.8Exploit: NoneExposed: 0

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.0(high)
EPSS
99.9%
KEV
Not listed

Published

July 8, 2008

Last Modified

April 23, 2026

Advisory Details (2)

Auto-updated May 30, 2026
Patch available.
generic Patch Available

#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 / EcosystemFixed in / 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.

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 4× in last 7d / 20× 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-11 08:22 UTCEPSS rescore
  2. 2026-07-11 08:22 UTCEPSS rescore
  3. 2026-07-09 19:04 UTCEPSS rescore
  4. 2026-07-08 01:35 UTCOSV refresh
  5. 2026-07-01 15:02 UTCEPSS rescore
  6. 2026-07-01 15:02 UTCEPSS rescore
  7. 2026-06-30 23:19 UTCEPSS rescore
  8. 2026-06-29 14:02 UTCEPSS rescore
  9. 2026-06-29 14:02 UTCEPSS rescore
  10. 2026-06-28 14:03 UTCEPSS rescore
  11. 2026-06-28 04:52 UTCEPSS rescore
  12. 2026-06-23 21:29 UTCEPSS rescore
  13. 2026-06-23 21:29 UTCEPSS rescore
  14. 2026-06-19 13:25 UTCOSV refresh
  15. 2026-06-17 17:49 UTCEPSS rescore
  16. 2026-06-17 17:49 UTCEPSS rescore
  17. 2026-06-15 17:44 UTCEPSS rescore
  18. 2026-06-14 23:13 UTCEPSS rescore
  19. 2026-06-12 23:08 UTCEPSS rescore
  20. 2026-06-12 23:08 UTCEPSS rescore
  21. 2026-06-10 22:14 UTCEPSS rescore
  22. 2026-06-10 13:17 UTCEPSS rescore
  23. 2026-06-08 14:13 UTCEPSS rescore
  24. 2026-06-07 15:22 UTCEPSS rescore
  25. 2026-06-05 22:44 UTCEPSS rescore
Show 22 more
  1. 2026-06-05 22:44 UTCEPSS rescore
  2. 2026-06-05 06:07 UTCEPSS rescore
  3. 2026-06-04 13:09 UTCEPSS rescore
  4. 2026-06-04 13:09 UTCEPSS rescore
  5. 2026-06-01 13:49 UTCEPSS rescore
  6. 2026-06-01 13:49 UTCEPSS rescore
  7. 2026-06-01 13:49 UTCEPSS rescore
  8. 2026-05-31 22:28 UTCEPSS rescore
  9. 2026-05-31 22:28 UTCEPSS rescore
  10. 2026-05-30 21:08 UTCEG score recompute
  11. 2026-05-30 21:08 UTCVendor advisory
  12. 2026-05-30 21:08 UTCGHSA enrichment
  13. 2026-05-29 13:40 UTCEPSS rescore
  14. 2026-05-28 13:42 UTCEPSS rescore
  15. 2026-05-28 13:42 UTCEPSS rescore
  16. 2026-05-28 13:42 UTCEPSS rescore
  17. 2026-05-27 13:38 UTCEPSS rescore
  18. 2026-05-27 13:37 UTCEPSS rescore
  19. 2026-05-26 07:16 UTCEPSS rescore
  20. 2026-05-26 07:16 UTCEPSS rescore
  21. 2026-05-22 17:43 UTCOSV refresh
  22. 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_host✓ verified
    First seen Jul 21, 2008

    DNS BailiWicked Host Attack

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

    DNS BailiWicked Domain Attack

    Open source ↗

Frequently asked(5)

What is CVE-2008-1447?
CVE-2008-1447 is a medium 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 in the National Vulnerability Database 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. FIRST EPSS estimates a 99.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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.
How do I remediate CVE-2008-1447?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2008-1447, 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-1447

Explore →

Is Your Infrastructure Affected by CVE-2008-1447?

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

Start Free Scan →Browse All CVEs