CVE-2009-3103

HIGHCVSS v2 · 10.010.0—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 10.0 — v2 rates that HIGH (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:L/Au:N/C:C/I:C/A:C. 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 90.1% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
Weaponized
10.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 90%
  • Public exploit code is available (Metasploit, Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 90%CVSS v2: 10.0Exploit: Metasploit · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Array index error in the SMBv2 protocol implementation in srv2.sys in Microsoft Windows Vista Gold, SP1, and SP2, Windows Server 2008 Gold and SP2, and Windows 7 RC allows remote attackers to execute arbitrary code or cause a denial of service (system crash) via an & (ampersand) character in a Process ID High header field in a NEGOTIATE PROTOCOL REQUEST packet, which triggers an attempted dereference of an out-of-bounds memory location, aka "SMBv2 Negotiation Vulnerability." NOTE: some of these details are obtained from third party information.

CVSS v2.0 (legacy)
10.0HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
10.0(low)
EG Risk
86(Track)
EG Risk 86/100SSVC: Track

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
Severity100% × 45%
Exploitation90% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
90%
EPSS %ILE
100%
KEV
Not listed

Published

September 8, 2009

Last Modified

April 23, 2026

References (36)

Data Freshness Timeline

(refreshed 0× in last 7d / 4× 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-08-19 16:58 UTCEPSS rescore
  2. 2026-08-08 16:31 UTCEPSS rescore
  3. 2026-08-03 10:28 UTCEPSS rescore
  4. 2026-07-30 01:26 UTCEPSS rescore
  5. 2026-07-26 13:38 UTCEG score recompute▲ 10.00
  6. 2026-07-25 14:12 UTCEPSS rescore
  7. 2026-07-24 14:12 UTCEPSS rescore
  8. 2026-07-23 14:14 UTCEPSS rescore
  9. 2026-07-23 01:06 UTCGHSA enrichment
  10. 2026-07-23 01:05 UTCGHSA enrichment
  11. 2026-07-23 01:04 UTCGHSA enrichment
  12. 2026-07-23 01:03 UTCGHSA enrichment
  13. 2026-07-23 01:02 UTCGHSA enrichment
  14. 2026-07-23 01:02 UTCGHSA enrichment
  15. 2026-07-23 01:01 UTCGHSA enrichment
  16. 2026-07-23 00:59 UTCGHSA enrichment
  17. 2026-07-23 00:58 UTCGHSA enrichment
  18. 2026-07-23 00:57 UTCGHSA enrichment
  19. 2026-07-23 00:56 UTCGHSA enrichment
  20. 2026-07-23 00:55 UTCGHSA enrichment
  21. 2026-07-23 00:54 UTCGHSA enrichment
  22. 2026-07-23 00:53 UTCGHSA enrichment
  23. 2026-07-23 00:52 UTCGHSA enrichment
  24. 2026-07-23 00:51 UTCGHSA enrichment
  25. 2026-07-23 00:50 UTCGHSA enrichment
Show 55 more
  1. 2026-07-23 00:49 UTCGHSA enrichment
  2. 2026-07-23 00:48 UTCGHSA enrichment
  3. 2026-07-23 00:47 UTCGHSA enrichment
  4. 2026-07-23 00:45 UTCGHSA enrichment
  5. 2026-07-23 00:44 UTCGHSA enrichment
  6. 2026-07-23 00:43 UTCGHSA enrichment
  7. 2026-07-23 00:43 UTCGHSA enrichment
  8. 2026-07-23 00:42 UTCEG score recompute
  9. 2026-07-23 00:42 UTCGHSA enrichment
  10. 2026-07-23 00:40 UTCGHSA enrichment
  11. 2026-07-23 00:37 UTCGHSA enrichment
  12. 2026-07-23 00:37 UTCEG score recompute▼ 9.00
  13. 2026-07-23 00:04 UTCEG score recompute
  14. 2026-07-22 21:43 UTCEG score recompute
  15. 2026-07-22 14:03 UTCEPSS rescore
  16. 2026-07-21 15:20 UTCEPSS rescore
  17. 2026-07-20 17:03 UTCEPSS rescore
  18. 2026-07-20 17:03 UTCEPSS rescore
  19. 2026-07-15 16:54 UTCEPSS rescore
  20. 2026-07-15 16:54 UTCEPSS rescore
  21. 2026-07-11 08:22 UTCEPSS rescore
  22. 2026-07-11 08:22 UTCEPSS rescore
  23. 2026-07-01 15:02 UTCEPSS rescore
  24. 2026-06-29 14:02 UTCEPSS rescore
  25. 2026-06-29 14:02 UTCEPSS rescore
  26. 2026-06-28 04:52 UTCEPSS rescore
  27. 2026-06-28 04:52 UTCEPSS rescore
  28. 2026-06-25 13:46 UTCEPSS rescore
  29. 2026-06-25 13:46 UTCEPSS rescore
  30. 2026-06-24 14:02 UTCEPSS rescore
  31. 2026-06-24 14:02 UTCEPSS rescore
  32. 2026-06-23 21:29 UTCEPSS rescore
  33. 2026-06-23 21:29 UTCEPSS rescore
  34. 2026-06-16 17:49 UTCEPSS rescore
  35. 2026-06-16 17:49 UTCEPSS rescore
  36. 2026-06-15 17:44 UTCEPSS rescore
  37. 2026-06-14 23:14 UTCEPSS rescore
  38. 2026-06-14 23:14 UTCEPSS rescore
  39. 2026-06-10 22:14 UTCEPSS rescore
  40. 2026-06-08 14:13 UTCEPSS rescore
  41. 2026-06-05 22:44 UTCEPSS rescore
  42. 2026-06-05 22:44 UTCEPSS rescore
  43. 2026-05-31 00:13 UTCEPSS rescore
  44. 2026-05-31 00:13 UTCEPSS rescore
  45. 2026-05-30 15:25 UTCEG score recompute
  46. 2026-05-30 15:25 UTCGHSA enrichment
  47. 2026-05-29 13:40 UTCEPSS rescore
  48. 2026-05-28 13:42 UTCEPSS rescore
  49. 2026-05-28 13:42 UTCEPSS rescore
  50. 2026-05-28 13:42 UTCEPSS rescore
  51. 2026-05-27 13:38 UTCEPSS rescore
  52. 2026-05-27 13:38 UTCEPSS rescore
  53. 2026-05-20 22:37 UTCEPSS rescore
  54. 2026-05-20 22:37 UTCEPSS rescore
  55. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(10 references)

Working exploit code is in the public domain (3 Metasploit modules) (1 GitHub PoC) (6 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCSic4rio/CVE-2009-3103---srv2.sys-SMB-Code-Execution-Python-MS09-050-
    First seen Dec 20, 2023

    Microsoft Windows - 'srv2.sys' SMB Code Execution (Python) (MS09-050)

    Open source ↗
  • Exploit-DBEDB-40280
    First seen Feb 26, 2016

    Microsoft Windows - 'srv2.sys' SMB Code Execution (Python) (MS09-050)

    Open source ↗
  • Exploit-DBEDB-14674
    First seen Aug 17, 2010

    Microsoft Windows - 'srv2.sys' SMB Negotiate ProcessID Function Table Dereference (MS09-050)

    Open source ↗
  • Exploit-DBEDB-16363✓ verified
    First seen Jul 3, 2010

    Microsoft Windows - 'srv2.sys' SMB Negotiate ProcessID Function Table Dereference (MS09-050) (Metasploit)

    Open source ↗
  • Exploit-DBEDB-12524✓ verified
    First seen May 7, 2010

    Microsoft Windows - SMB2 Negotiate Protocol '0x72' Response Denial of Service

    Open source ↗
  • Exploit-DBEDB-10005✓ verified
    First seen Nov 11, 2009

    Microsoft Windows 7/2008 R2 - Remote Kernel Crash

    Open source ↗
  • Exploit-DBEDB-9594✓ verified
    First seen Sep 9, 2009

    Microsoft Windows Vista/7 - SMB2.0 Negotiate Protocol Request Remote Blue Screen of Death (MS07-063)

    Open source ↗
  • Metasploitexploit/windows/smb/ms09_050_smb2_negotiate_func_index✓ verified
    First seen Sep 7, 2009

    MS09-050 Microsoft SRV2.SYS SMB Negotiate ProcessID Function Table Dereference

    Open source ↗
  • Metasploitauxiliary/dos/windows/smb/ms09_050_smb2_negotiate_pidhigh✓ verified
    First seen Jan 1, 2009

    Microsoft SRV2.SYS SMB Negotiate ProcessID Function Table Dereference

    Open source ↗
  • Metasploitauxiliary/dos/windows/smb/ms09_050_smb2_session_logoff✓ verified
    First seen Jan 1, 2009

    Microsoft SRV2.SYS SMB2 Logoff Remote Kernel NULL Pointer Dereference

    Open source ↗

Frequently asked(4)

What is CVE-2009-3103?
CVE-2009-3103 is a high vulnerability published on September 8, 2009. Array index error in the SMBv2 protocol implementation in srv2.sys in Microsoft Windows Vista Gold, SP1, and SP2, Windows Server 2008 Gold and SP2, and Windows 7 RC allows remote attackers to execute arbitrary code or cause a denial of service (system crash) via an & (ampersand) character in a…
When was CVE-2009-3103 disclosed?
CVE-2009-3103 was first published in the National Vulnerability Database on September 8, 2009, 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-2009-3103 actively exploited?
CVE-2009-3103 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 90% probability of exploitation in the next 30 days, which ranks it in the top 0.2% of all scored CVEs.
How do I remediate CVE-2009-3103?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2009-3103, 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-2009-3103

Explore →

Is Your Infrastructure Affected by CVE-2009-3103?

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

Start Free Scan →Browse All CVEs