Evidence used
- No CISA KEV confirmation is currently recorded.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 95.18% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2008
CVE-2008-1447High confidence
Affected product: Insufficient Entropy
Unknown · Unknown
6.8MediumCVSS 3.1
Scheduled
Patch availableMedium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityMedium→Operational priority:High, raised one band.upgradedsince 4 Oct 2026
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Unknown Unknown and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Distribution package intelligence
28 package statesRelease-specific package status
Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | adns | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.4-2 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian trixietrixie · source | bind9 | Vendor fix publishedDebian records a fixed source-package version for this release. | 1:9.5.0.dfsg-5 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian trixietrixie · source | dnsmasq | Vendor fix publishedDebian records a fixed source-package version for this release. | 2.43-1 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian trixietrixie · source | dnspython | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.7.1-1 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian trixietrixie · source | libnet-dns-perl | Vendor fix publishedDebian records a fixed source-package version for this release. | 0.63-2 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian trixietrixie · source | refpolicy | Vendor fix publishedDebian records a fixed source-package version for this release. | 2:0.0.20080702-1 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian trixietrixie · source | udns | Vendor fix publishedDebian records a fixed source-package version for this release. | 0.2-1 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian bookwormbookworm · source | adns | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.4-2 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian bookwormbookworm · source | bind9 | Vendor fix publishedDebian records a fixed source-package version for this release. | 1:9.5.0.dfsg-5 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian bookwormbookworm · source | dnsmasq | Vendor fix publishedDebian records a fixed source-package version for this release. | 2.43-1 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian bookwormbookworm · source | dnspython | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.7.1-1 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian bookwormbookworm · source | libnet-dns-perl | Vendor fix publishedDebian records a fixed source-package version for this release. | 0.63-2 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian bookwormbookworm · source | refpolicy | Vendor fix publishedDebian records a fixed source-package version for this release. | 2:0.0.20080702-1 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian bookwormbookworm · source | udns | Vendor fix publishedDebian records a fixed source-package version for this release. | 0.2-1 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian forkyforky · source | adns | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.4-2 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian forkyforky · source | bind9 | Vendor fix publishedDebian records a fixed source-package version for this release. | 1:9.5.0.dfsg-5 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian forkyforky · source | dnsmasq | Vendor fix publishedDebian records a fixed source-package version for this release. | 2.43-1 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian forkyforky · source | dnspython | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.7.1-1 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian forkyforky · source | libnet-dns-perl | Vendor fix publishedDebian records a fixed source-package version for this release. | 0.63-2 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian forkyforky · source | refpolicy | Vendor fix publishedDebian records a fixed source-package version for this release. | 2:0.0.20080702-1 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian forkyforky · source | udns | Vendor fix publishedDebian records a fixed source-package version for this release. | 0.2-1 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian sidsid · source | adns | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.4-2 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian sidsid · source | bind9 | Vendor fix publishedDebian records a fixed source-package version for this release. | 1:9.5.0.dfsg-5 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian sidsid · source | dnsmasq | Vendor fix publishedDebian records a fixed source-package version for this release. | 2.43-1 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian sidsid · source | dnspython | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.7.1-1 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian sidsid · source | libnet-dns-perl | Vendor fix publishedDebian records a fixed source-package version for this release. | 0.63-2 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian sidsid · source | refpolicy | Vendor fix publishedDebian records a fixed source-package version for this release. | 2:0.0.20080702-1 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian sidsid · source | udns | Vendor fix publishedDebian records a fixed source-package version for this release. | 0.2-1 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Patch available01
What, why and how
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."
What
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."
Why
The product uses an algorithm or scheme that produces insufficient entropy, leaving patterns or clusters of values that are more likely to occur than others.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
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."
Why
The product uses an algorithm or scheme that produces insufficient entropy, leaving patterns or clusters of values that are more likely to occur than others.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Insufficient Entropy → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- High: exploitation depends on specific conditions
- Security boundary
- Changed: exploitation can affect a different security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-331 ↗
CWE-331: Insufficient Entropy. The product uses an algorithm or scheme that produces insufficient entropy, leaving patterns or clusters of values that are more likely to occur than others.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:NCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SChangedScope: The attack can affect a component governed by a different security authority.CNoneConfidentiality impact: No direct loss is represented by this metric.IHighIntegrity impact: A successful attack can cause a major loss.ANoneAvailability impact: No direct loss is represented by this metric.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Affected
- n/a: n/a
- Action
- Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 8 Jul 2008 · Last source change 7 Aug 2024, 08:24 UTC · CWE-331 · Insufficient Entropy
CVE recordCVE.org · 5.1
CVSS sourceNIST NVD
EPSS source FIRST · tracked since 2026-09-13
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2008-1451
Product sourceUnavailable
Remediation sourceCVE/CNA references
CWE sourceNIST NVD
NVD statusNVD modified after enrichment
Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.
Material change intelligence
View recent updates ↗What changed after publication
- ENISA EUVD mappingEUVD-2008-1451 was added to the official ENISA EUVD mapping for this CVE.ENISA EUVD ↗
- Before
- not recorded
- After
- {"euvdId":"EUVD-2008-1451"}
- Vendor guidanceAuthoritative vendor guidance changed: added patch: debian.org/dsa-1603; added remediation: debian.org/dsa-1603; removed remediation: docs.microsoft.com/ms08-037; removed vendor advisory: cisco.com/products_security_advisory09186a00809c2168.shtml; 10 further additions; 39 further removals.debian.org ↗
- Before
- patch: docs.microsoft.com/ms08-037 · remediation: docs.microsoft.com/ms08-037 · vendor advisory: cisco.com/products_security_advisory09186a00809c2168.shtml · 39 more references
- After
- patch: debian.org/dsa-1603 · patch: docs.microsoft.com/ms08-037 · remediation: debian.org/dsa-1603 · 10 more references
- Public exploit evidencePublic exploit evidence changed from Public exploit reference to No public exploit.CVE.org ↗
- Before
- Public exploit reference
- After
- No public exploit
- SeveritySeverity changed from Unknown to Medium.NIST NVD ↗
- Before
- Unknown
- After
- Medium
- CVSS scoreCVSS score changed from not recorded to 6.8 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N).NIST NVD ↗
- Before
- not recorded
- After
- 6.8 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N)
- Catalogue recordCVE added to the BlackTree catalogue.CNA ↗
CVE published
Fixed release or patch reference recorded
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.