CVE-2006-0987

MEDIUMCVSS v2 · 5.05.0
EchelonGraph scoreLOW confidence

“—” beside the score: it is equal to NVD's CVSS v2 base score.

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 5.0 — NVD rates that MEDIUM (NVD's v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; no CRITICAL band). Vector AV:N/AC:L/Au:N/C:N/I:N/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 58% exploitation probability in the next 30 days; it does not lift the v2 base. EchelonGraph's fixed weight for EG-KEV Tier 2 (Weaponized) sets EG Risk's exploitation input, not EPSS. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: NVD CVSS v2.0
Trending — 3 sources updated this weekWeaponized

Also known asEUVD-2006-0990 (ENISA EUVD) · GHSA-rmj9-c82h-2f4h (GitHub Security Advisories)Source: ENISA EUVD

5.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 58%
  • Public exploit code is available (Metasploit)
CISA-KEV: Not listedEPSS PROB: 58%CVSS v2: 5.0Exploit: MetasploitExposed services: Not assessed

A fix is available — apply it.

The default configuration of ISC BIND before 9.4.1-P1, when configured as a caching name server, allows recursive queries and provides additional delegation information to arbitrary IP addresses, which allows remote attackers to cause a denial of service (traffic amplification) via DNS queries with spoofed source IP addresses.

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

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity50% × 45%
Impact severity (EG Severity): CVSS 5.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation65% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 2 (Weaponized): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (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
58%
EPSS %ILE
99th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.0): severity, escalated by confirmed exploitation. This CVE's 5.0 is its impact severity (EG Severity), not escalated.

EG Severity
5.0 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v2.0 · CVSS v2.0AV:N/AC:L/Au:N/C:N/I:N/A:P
EG Likelihood
58% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-07). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; 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 (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (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

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 3, 2006

Last Modified

October 9, 2026

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
bind9—
  • every version up to 1:9.4.0-1: fixed in 1:9.4.0-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
bind9—
  • every version up to 1:9.4.0-1: fixed in 1:9.4.0-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
bind9—
  • every version up to 1:9.4.0-1: fixed in 1:9.4.0-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
bind9—
  • every version up to 1:9.4.0-1: fixed in 1:9.4.0-1
—

Data Freshness Timeline

(refreshed 7× in last 7d / 32× 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 93 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. 7 repeat rows among the latest 100 are merged into the row they repeat. The 20 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-10 16:26 UTCEPSS rescoreEPSS 58% · 99th percentile
  2. 2026-11-08 02:39 UTCGHSA enrichmentGHSA-rmj9-c82h-2f4h · GitHub severity MODERATE
  3. 2026-11-08 02:39 UTCEG score recompute
  4. 2026-11-07 16:26 UTCEPSS rescoreEPSS 58% · 99th percentile
  5. 2026-11-06 16:25 UTCEPSS rescoreEPSS 58% · 99th percentile
  6. 2026-11-05 16:25 UTCEPSS rescoreEPSS 58% · 99th percentile
  7. 2026-11-04 16:25 UTCEPSS rescoreEPSS 58% · 99th percentile
  8. 2026-11-03 16:26 UTCEPSS rescoreEPSS 58% · 99th percentile
  9. 2026-10-31 16:25 UTCEPSS rescoreEPSS 58% · 99th percentile
  10. 2026-10-30 16:25 UTCEPSS rescoreEPSS 58% · 99th percentile
  11. 2026-10-29 16:25 UTCEPSS rescoreEPSS 58% · 99th percentile
  12. 2026-10-29 14:22 UTCEG score recompute
  13. 2026-10-29 14:22 UTCGHSA enrichmentGHSA-rmj9-c82h-2f4h
  14. 2026-10-28 16:25 UTCEPSS rescoreEPSS 58% · 99th percentile
  15. 2026-10-27 16:25 UTCEPSS rescoreEPSS 58% · 99th percentile
  16. 2026-10-27 06:25 UTCOSV refresh
  17. 2026-10-25 20:43 UTCEG score recompute
  18. 2026-10-25 16:25 UTCEPSS rescoreEPSS 58% · 99th percentile
  19. 2026-10-23 16:25 UTCEPSS rescoreEPSS 58% · 99th percentile
  20. 2026-10-22 16:25 UTCEPSS rescoreEPSS 58% · 99th percentile
  21. 2026-10-21 16:25 UTCEPSS rescoreEPSS 58% · 99th percentile
  22. 2026-10-20 16:25 UTCEPSS rescoreEPSS 58% · 99th percentile
  23. 2026-10-19 16:25 UTCEPSS rescoreEPSS 58% · 99th percentile
  24. 2026-10-18 12:10 UTCEG score recompute
  25. 2026-10-17 16:25 UTCEPSS rescoreEPSS 58% · 99th percentile
Show 68 more
  1. 2026-10-16 16:25 UTCEPSS rescoreEPSS 58% · 99th percentile
  2. 2026-10-15 16:25 UTCEPSS rescoreEPSS 58% · 99th percentile
  3. 2026-10-14 16:25 UTCEPSS rescoreEPSS 58% · 99th percentile
  4. 2026-10-13 16:25 UTCEPSS rescoreEPSS 58% · 99th percentile
  5. 2026-10-12 22:07 UTCEG score recompute
  6. 2026-10-12 16:25 UTCEPSS rescoreEPSS 58% · 99th percentile
  7. 2026-10-12 02:15 UTCEG score recompute
  8. 2026-10-11 13:37 UTCEPSS rescoreEPSS 58% · 99th percentile
  9. 2026-10-10 19:53 UTCEPSS rescoreEPSS 58% · 99th percentile
  10. 2026-10-09 20:34 UTCGHSA enrichmentGHSA-rmj9-c82h-2f4h
  11. 2026-10-09 20:33 UTCNVD update
  12. 2026-10-09 19:59 UTCEPSS rescoreEPSS 58% · 99th percentile
  13. 2026-10-09 19:19 UTCEG score recompute
  14. 2026-10-09 19:19 UTCGHSA enrichmentGHSA-rmj9-c82h-2f4h
  15. 2026-10-09 19:18 UTCMITRE cvelistV5
  16. 2026-10-08 16:32 UTCEPSS rescoreEPSS 58% · 99th percentile
  17. 2026-10-07 23:36 UTCEPSS rescoreEPSS 58% · 99th percentile
  18. 2026-10-06 15:08 UTCEPSS rescoreEPSS 58% · 99th percentile
  19. 2026-10-05 09:14 UTCOSV refresh
  20. 2026-10-03 14:19 UTCEPSS rescoreEPSS 58% · 99th percentile
  21. 2026-09-29 02:58 UTCEG score recompute
  22. 2026-09-18 19:20 UTCEPSS rescoreEPSS 58% · 99th percentile
  23. 2026-09-17 19:20 UTCEPSS rescoreEPSS 58% · 99th percentile
  24. 2026-09-15 16:24 UTCOSV refresh
  25. 2026-09-12 14:54 UTCEPSS rescoreEPSS 58% · 99th percentile
  26. 2026-09-10 09:23 UTCEPSS rescoreEPSS 58% · 99th percentile
  27. 2026-09-05 15:21 UTCEPSS rescoreEPSS 58% · 99th percentile
  28. 2026-08-30 01:14 UTCEPSS rescoreEPSS 58% · 99th percentile
  29. 2026-08-27 15:47 UTCOSV refresh
  30. 2026-08-11 05:31 UTCOSV refresh
  31. 2026-08-05 19:11 UTCEPSS rescoreEPSS 57% · 98th percentile
  32. 2026-07-26 13:28 UTCEG score recomputeAssessed again: 5.0 MEDIUM
  33. 2026-07-26 05:42 UTCOSV refresh
  34. 2026-07-24 14:11 UTCEPSS rescoreEPSS 57% · 98th percentile
  35. 2026-07-23 00:49 UTCEG score recompute
  36. 2026-07-23 00:29 UTCEG score recompute▼ 4.50
  37. 2026-07-22 23:53 UTCEG score recomputeFirst assessed: 4.5 MEDIUM
  38. 2026-07-22 21:33 UTCEG score recompute
  39. 2026-07-20 17:02 UTCEPSS rescoreEPSS 57% · 98th percentile
  40. 2026-07-16 16:58 UTCEPSS rescoreEPSS 57% · 98th percentile
  41. 2026-07-15 16:53 UTCEPSS rescoreEPSS 57% · 98th percentile
  42. 2026-07-13 22:25 UTCEPSS rescoreEPSS 57% · 98th percentile
  43. 2026-07-13 06:07 UTCEPSS rescoreEPSS 57% · 98th percentile
  44. 2026-07-11 08:22 UTCEPSS rescoreEPSS 57% · 98th percentile
  45. 2026-07-09 19:03 UTCEPSS rescoreEPSS 57% · 98th percentile
  46. 2026-07-09 00:09 UTCOSV refresh
  47. 2026-07-08 15:09 UTCEPSS rescoreEPSS 57% · 98th percentile
  48. 2026-07-02 14:00 UTCEPSS rescoreEPSS 57% · 98th percentile
  49. 2026-07-01 15:01 UTCEPSS rescoreEPSS 57% · 98th percentile
  50. 2026-06-27 03:04 UTCEPSS rescoreEPSS 57% · 98th percentile
  51. 2026-06-25 13:46 UTCEPSS rescoreEPSS 57% · 98th percentile
  52. 2026-06-23 21:29 UTCEPSS rescoreEPSS 57% · 98th percentile
  53. 2026-06-22 14:22 UTCEPSS rescoreEPSS 57% · 98th percentile
  54. 2026-06-21 01:56 UTCEPSS rescoreEPSS 57% · 98th percentile
  55. 2026-06-20 12:12 UTCOSV refresh
  56. 2026-06-17 17:49 UTCEPSS rescoreEPSS 57% · 98th percentile
  57. 2026-06-16 17:49 UTCEPSS rescoreEPSS 57% · 98th percentile
  58. 2026-06-15 17:44 UTCEPSS rescoreEPSS 57% · 98th percentile
  59. 2026-06-13 22:56 UTCEPSS rescoreEPSS 31% · 96th percentile
  60. 2026-06-12 23:08 UTCEPSS rescoreEPSS 31% · 96th percentile
  61. 2026-06-11 13:55 UTCEPSS rescoreEPSS 31% · 96th percentile
  62. 2026-06-10 22:14 UTCEPSS rescoreEPSS 31% · 96th percentile
  63. 2026-06-10 13:17 UTCEPSS rescoreEPSS 31% · 96th percentile
  64. 2026-06-06 13:44 UTCEPSS rescoreEPSS 31% · 96th percentile
  65. 2026-06-05 22:43 UTCEPSS rescoreEPSS 31% · 96th percentile
  66. 2026-06-04 13:09 UTCEPSS rescoreEPSS 31% · 96th percentile
  67. 2026-06-02 20:10 UTCEPSS rescoreEPSS 31% · 96th percentile
  68. 2026-06-01 13:49 UTCEPSS rescoreEPSS 31% · 96th percentile

Publicly available exploits

(2 references)

Public exploit code is referenced for this CVE (1 Metasploit module), as is 1 GitHub checker repository. A GitHub repository named or described as a checker or scanner checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • Metasploitauxiliary/scanner/dns/dns_amp✓ verified
    Published Mar 31, 2014

    DNS Amplification Scanner

    Open source ↗
  • GitHub checkerpcastagnaro/dns_amplification_scanner
    Published Sep 20, 2024

    This script checks if each domain from a given domain list is vulnerable to CVE-2006-0987

    Open source ↗

Frequently asked(4)

What is CVE-2006-0987?
CVE-2006-0987 is a medium-severity vulnerability; its CVE record was published on March 3, 2006. The default configuration of ISC BIND before 9.4.1-P1, when configured as a caching name server, allows recursive queries and provides additional delegation information to arbitrary IP addresses, which allows remote attackers to cause a denial of service (traffic amplification) via DNS queries with…
When was CVE-2006-0987 made public?
CVE-2006-0987 was made public on February 28, 2006: 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 March 3, 2006. EchelonGraph's copy of the record carries a last-modified date of October 9, 2026; the record at its source may have been updated since.
Is CVE-2006-0987 actively exploited?
CVE-2006-0987 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: a Metasploit module exists for it. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 58% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
How do I remediate CVE-2006-0987?
A fix for CVE-2006-0987 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-2006-0987

Explore →

Is Your Infrastructure Affected by CVE-2006-0987?

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