CVE-2008-4250

CRITICALNVD 9.89.8
EchelonGraph scoreHIGH confidence

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

Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2026-05-20), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Exploited in the wild
9.8EG
EchelonGraph verdictMitigate nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low mission impact
CISA-KEV: ExploitedEPSS PROB: 99%CVSS: 9.8Exploit: Metasploit · Exploit-DB (verified) · other public PoCExposed 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 Server service in Microsoft Windows 2000 SP4, XP SP2 and SP3, Server 2003 SP1 and SP2, Vista Gold and SP1, Server 2008, and 7 Pre-Beta allows remote attackers to execute arbitrary code via a crafted RPC request that triggers the overflow during path canonicalization, as exploited in the wild by Gimmiv.A in October 2008, aka "Server Service Vulnerability."

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
99
EG Risk 99/100

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 (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Attend at low mission impact; Act at medium or high.
Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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 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 sooner than your standard update timelines at low mission impact and as soon as possible at medium or high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
99%
EPSS %ILE
99th
KEV
⚠ Exploited

SSVC (CISA's decision table, applied by EchelonGraph)Attend at low mission impact; Act at medium or high.

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 sooner than your standard update timelines at low mission impact and as soon as possible at medium or high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 days & forensic triage if the affected system is publicly exposed; 3 days & forensic triage if it is not.

In CISA KEV yes (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (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

CISA required action“Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://learn.microsoft.com/en-us/security-updates/securitybulletins/2008/ms08-067 · https://nvd.nist.gov/vuln/detail/CVE-2008-4250

Published

October 23, 2008

Last Modified

May 21, 2026

Advisory Details (7)

Auto-updated Oct 8, 2026
Fix referenced — no release confirmed yet. Sources: cert.
Web page

CVE-2008-4250 - PSIRT.COM

http://www.securityfocus.com/bid/31874
Web page

SecurityFocus

http://www.securityfocus.com/archive/1/497816/100/0/threaded
Web page

SecurityFocus

http://www.securityfocus.com/archive/1/497808/100/0/threaded
CERT

VU#827267 - Microsoft Server service RPC stack buffer overflow vulnerability

http://www.kb.cert.org/vuls/id/827267
Web page

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

http://marc.info/?l=bugtraq&m=122703006921213&w=2
Web page

Secunia Research & Vulnerability Insights | Flexera

http://secunia.com/advisories/32326
Web page
http://www.securitytracker.com/id?1021091

Vendor Advisories for CVE-2008-4250(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 49× in last 7d / 214× 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 100 of 965 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. None are among the latest 100 rows. The 865 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(8 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 6 Exploit-DB entries, 1 GitHub PoC). No release with the fix is confirmed, so defenders should restrict or isolate affected systems accordingly until one is applied.

  • Exploit-DBEDB-16362✓ verified
    Published Jan 21, 2011

    Microsoft Windows Server - Service Relative Path Stack Corruption (MS08-067) (Metasploit)

    Open source ↗
  • Exploit-DBEDB-7132✓ verified
    Published Nov 16, 2008

    Microsoft Windows Server 2000/2003 - Code Execution (MS08-067)

    Open source ↗
  • Exploit-DBEDB-7104✓ verified
    Published Nov 12, 2008

    Microsoft Windows Server - Code Execution (MS08-067)

    Open source ↗
  • Metasploitexploit/windows/smb/ms08_067_netapi✓ verified
    Published Oct 28, 2008

    MS08-067 Microsoft Server Service Relative Path Stack Corruption

    Open source ↗
  • Exploit-DBEDB-6841✓ verified
    Published Oct 26, 2008

    Microsoft Windows Server - Universal Code Execution (MS08-067)

    Open source ↗
  • Exploit-DBEDB-6824✓ verified
    Published Oct 23, 2008

    Microsoft Windows Server - Code Execution (PoC) (MS08-067)

    Open source ↗
  • GitHub PoCBinRacer/ms08-067.py
    Published Sep 6, 2025

    This repository contains some python scripts implementation for the MS08-067 Windows Server Service vulnerability (CVE-2008-4250). This is a classic remote code execution vulnerability affecting older Windows systems.

    Open source ↗
  • Exploit-DBEDB-40279
    Published Feb 26, 2016

    Microsoft Windows - 'NetAPI32.dll' Code Execution (Python) (MS08-067)

    Open source ↗

Related CVEs(same CWE)

Frequently asked(6)

What is CVE-2008-4250?
CVE-2008-4250 is a critical-severity vulnerability; its CVE record was published on October 23, 2008. The Server service in Microsoft Windows 2000 SP4, XP SP2 and SP3, Server 2003 SP1 and SP2, Vista Gold and SP1, Server 2008, and 7 Pre-Beta allows remote attackers to execute arbitrary code via a crafted RPC request that triggers the overflow during path canonicalization, as exploited in the wild by…
When was CVE-2008-4250 made public?
CVE-2008-4250 was made public on October 23, 2008: that is the date its CVE record's CNA, Microsoft Corporation, gives for when the vulnerability was made public. The CVE record itself was published on October 23, 2008. EchelonGraph's copy of the record carries a last-modified date of May 21, 2026; the record at its source may have been updated since.
Is CVE-2008-4250 actively exploited?
Yes. CISA added CVE-2008-4250 to the Known Exploited Vulnerabilities catalog on May 20, 2026, affecting Microsoft Windows. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. 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; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
What is the CVSS score of CVE-2008-4250?
CVE-2008-4250 has a CVSS v3 base score of 9.8 (NVD).
Which products are affected by CVE-2008-4250?
CVE-2008-4250 affects Microsoft Windows.
How do I remediate CVE-2008-4250?
A fix for CVE-2008-4250 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. The vendor advisories EchelonGraph has for CVE-2008-4250 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2008-4250?

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

Book a Demo →Browse All CVEs