CVE-2008-0087

HIGHNVD 7.57.6▲
EchelonGraph scoreHIGH confidence

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

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: epss, ghsa, nvd
Elevated
7.6EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 32%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

The DNS client in Microsoft Windows 2000 SP4, XP SP2, Server 2003 SP1 and SP2, and Vista uses predictable DNS transaction IDs, which allows remote attackers to spoof DNS responses.

CVSS v3
7.5
EG Score
7.6HIGHhigh confidence
EG Risk
55
EG Risk 55/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
Severity76% × 45%
Exploitation40% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
32%
EPSS %ILE
98th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation public PoC (EG-KEV: elevated) · 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

April 8, 2008

Last Modified

April 23, 2026

Advisory Details (7)

Auto-updated May 30, 2026
🔬 Proof of concept available. Fix referenced — no release confirmed yet.
generic🟡 PoC Available

Microsoft Security Bulletin MS08-020 - Important | Microsoft Learn

https://docs.microsoft.com/en-us/security-updates/securitybulletins/2008/ms08-020
generic

VUPEN Security - Vulnerability Research and Intelligence

http://www.vupen.com/english/advisories/2008/1144/references
generic
http://www.securitytracker.com/id?1019802
generic
http://www.securityfocus.com/bid/28553
generic
http://www.securityfocus.com/archive/1/490575/100/0/threaded
generic

About Secunia Research | Flexera

http://secunia.com/advisories/29696
generic

'[security bulletin] HPSBST02329 SSRT080048 rev.1 - Storage Management Appliance (SMA), Microsoft Pat' - MARC

http://marc.info/?l=bugtraq&m=120845064910729&w=2

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 12× 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.

Showing the most recent 100 of 105 total refreshes for this CVE.

  1. 2026-10-09 20:00 UTCEPSS rescore
  2. 2026-10-08 16:33 UTCEPSS rescore
  3. 2026-10-07 23:37 UTCEPSS rescore
  4. 2026-10-06 15:09 UTCEPSS rescore
  5. 2026-10-03 14:20 UTCEPSS rescore
  6. 2026-10-01 19:42 UTCEPSS rescore
  7. 2026-09-30 14:57 UTCEPSS rescore
  8. 2026-09-29 07:46 UTCEG score recompute
  9. 2026-09-18 19:20 UTCEPSS rescore
  10. 2026-09-17 19:20 UTCEPSS rescore
  11. 2026-09-15 03:04 UTCEPSS rescore
  12. 2026-09-12 14:54 UTCEPSS rescore
  13. 2026-09-05 15:22 UTCEPSS rescore
  14. 2026-09-04 13:55 UTCEPSS rescore
  15. 2026-09-04 04:59 UTCEPSS rescore
  16. 2026-08-30 01:14 UTCEPSS rescore
  17. 2026-08-08 16:30 UTCEPSS rescore
  18. 2026-08-07 16:20 UTCEPSS rescore
  19. 2026-08-06 13:41 UTCEPSS rescore
  20. 2026-08-05 19:11 UTCEPSS rescore
  21. 2026-08-04 15:03 UTCEPSS rescore
  22. 2026-07-30 16:22 UTCEPSS rescore
  23. 2026-07-30 01:25 UTCEPSS rescore
  24. 2026-07-28 15:30 UTCEPSS rescore
  25. 2026-07-25 14:12 UTCEPSS rescore
Show 75 more
  1. 2026-07-24 14:11 UTCEPSS rescore
  2. 2026-07-23 14:13 UTCEPSS rescore
  3. 2026-07-23 00:55 UTCEG score recompute
  4. 2026-07-23 00:34 UTCEG score recompute
  5. 2026-07-22 23:59 UTCEG score recompute▲ 0.10
  6. 2026-07-22 21:39 UTCEG score recompute
  7. 2026-07-22 14:03 UTCEPSS rescore
  8. 2026-07-21 15:19 UTCEPSS rescore
  9. 2026-07-20 17:03 UTCEPSS rescore
  10. 2026-07-18 09:59 UTCEPSS rescore
  11. 2026-07-16 16:58 UTCEPSS rescore
  12. 2026-07-15 16:54 UTCEPSS rescore
  13. 2026-07-15 16:54 UTCEPSS rescore
  14. 2026-07-13 06:07 UTCEPSS rescore
  15. 2026-07-11 08:22 UTCEPSS rescore
  16. 2026-07-08 15:09 UTCEPSS rescore
  17. 2026-07-06 16:22 UTCEPSS rescore
  18. 2026-07-05 02:26 UTCEPSS rescore
  19. 2026-07-02 14:00 UTCEPSS rescore
  20. 2026-07-01 15:02 UTCEPSS rescore
  21. 2026-07-01 15:02 UTCEPSS rescore
  22. 2026-06-28 04:52 UTCEPSS rescore
  23. 2026-06-27 03:04 UTCEPSS rescore
  24. 2026-06-25 13:46 UTCEPSS rescore
  25. 2026-06-25 13:46 UTCEPSS rescore
  26. 2026-06-24 14:02 UTCEPSS rescore
  27. 2026-06-24 14:02 UTCEPSS rescore
  28. 2026-06-23 21:29 UTCEPSS rescore
  29. 2026-06-23 21:29 UTCEPSS rescore
  30. 2026-06-22 14:22 UTCEPSS rescore
  31. 2026-06-21 14:53 UTCEPSS rescore
  32. 2026-06-21 01:56 UTCEPSS rescore
  33. 2026-06-21 01:56 UTCEPSS rescore
  34. 2026-06-18 17:49 UTCEPSS rescore
  35. 2026-06-18 17:49 UTCEPSS rescore
  36. 2026-06-17 17:49 UTCEPSS rescore
  37. 2026-06-17 17:49 UTCEPSS rescore
  38. 2026-06-16 17:49 UTCEPSS rescore
  39. 2026-06-16 17:49 UTCEPSS rescore
  40. 2026-06-16 17:49 UTCEPSS rescore
  41. 2026-06-15 17:44 UTCEPSS rescore
  42. 2026-06-13 22:57 UTCEPSS rescore
  43. 2026-06-12 23:08 UTCEPSS rescore
  44. 2026-06-10 22:14 UTCEPSS rescore
  45. 2026-06-07 15:21 UTCEPSS rescore
  46. 2026-06-06 13:44 UTCEPSS rescore
  47. 2026-06-06 13:44 UTCEPSS rescore
  48. 2026-06-05 22:44 UTCEPSS rescore
  49. 2026-06-05 22:44 UTCEPSS rescore
  50. 2026-06-05 06:07 UTCEPSS rescore
  51. 2026-06-04 13:09 UTCEPSS rescore
  52. 2026-06-04 13:09 UTCEPSS rescore
  53. 2026-06-04 13:09 UTCEPSS rescore
  54. 2026-06-02 20:10 UTCEPSS rescore
  55. 2026-06-02 20:10 UTCEPSS rescore
  56. 2026-06-01 13:49 UTCEPSS rescore
  57. 2026-06-01 13:49 UTCEPSS rescore
  58. 2026-06-01 13:49 UTCEPSS rescore
  59. 2026-05-31 00:13 UTCEPSS rescore
  60. 2026-05-31 00:13 UTCEPSS rescore
  61. 2026-05-30 22:12 UTCEG score recompute
  62. 2026-05-30 22:12 UTCGHSA enrichment
  63. 2026-05-29 13:40 UTCEPSS rescore
  64. 2026-05-28 13:42 UTCEPSS rescore
  65. 2026-05-28 13:42 UTCEPSS rescore
  66. 2026-05-28 13:42 UTCEPSS rescore
  67. 2026-05-27 13:38 UTCEPSS rescore
  68. 2026-05-27 13:37 UTCEPSS rescore
  69. 2026-05-27 13:37 UTCEPSS rescore
  70. 2026-05-26 07:16 UTCEPSS rescore
  71. 2026-05-26 07:16 UTCEPSS rescore
  72. 2026-05-24 16:42 UTCEPSS rescore
  73. 2026-05-22 21:15 UTCEPSS rescore
  74. 2026-05-22 21:15 UTCEPSS rescore
  75. 2026-05-20 22:36 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2008-0087?
CVE-2008-0087 is a high vulnerability published on April 8, 2008. The DNS client in Microsoft Windows 2000 SP4, XP SP2, Server 2003 SP1 and SP2, and Vista uses predictable DNS transaction IDs, which allows remote attackers to spoof DNS responses.
When was CVE-2008-0087 disclosed?
CVE-2008-0087 was first published on April 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-0087 actively exploited?
CVE-2008-0087 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 32% probability of exploitation in the next 30 days (98th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2008-0087?
CVE-2008-0087 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.6 (HIGH).
How do I remediate CVE-2008-0087?
A fix for CVE-2008-0087 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2008-0087

Explore →

Is Your Infrastructure Affected by CVE-2008-0087?

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

Book a Demo →Browse All CVEs