How severe is CVE-2009-3103?

No CVSS score has been assigned to CVE-2009-3103 yet. Review the advisory details and affected package list to assess your exposure.

Which products are affected by CVE-2009-3103?

CVE-2009-3103 affects the following products: microsoft windows server 2008, microsoft windows vista.

How do I patch CVE-2009-3103?

No patch has shipped for CVE-2009-3103 yet — track the microsoft windows server 2008 advisory for a fixed release and apply the workarounds below in the meantime.

How do I detect CVE-2009-3103 across my infrastructure?

Inventory every microsoft windows server 2008 deployment and check each version against the affected-products list above.

How do I mitigate CVE-2009-3103 if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Is CVE-2009-3103 actively exploited in the wild?

Yes. There are 13 known exploit references for CVE-2009-3103, including 6 documented proof-of-concept exploits on Exploit-DB and 6 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2009-3103?

CVE-2009-3103 has an EPSS (Exploit Prediction Scoring System) score of 92.3%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2009-3103?

CVE-2009-3103 is classified as CWE-399 (CWE-399). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2009-3103?

CVE-2009-3103 affects microsoft windows server 2008 (1 version, e.g. sp2); microsoft windows vista. Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2009-3103 published, and has it been updated?

CVE-2009-3103 was published on September 8, 2009 and was last updated on June 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Not in CISA KEV

CVE-2009-3103 — Windows Server 2008

CVE-2009-3103 is a CWE-399 vulnerability in microsoft windows server 2008. 13 public exploit references exist, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

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…

Published

Sep 8, 2009

Updated

Jun 16, 2026

Affected

2 products

Patched

See advisory

Exploits

13 known

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

92.3%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

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.

Affected Products

2 products · 10 configurations

windows server 2008microsoft

1 version

sp2

windows vistamicrosoft

all

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-12524doswindows✓ Verified

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

by Jelmer de Hen · May 7, 2010

Exploit-DB Source

EDB-14674remotewindows

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

by Piotr Bania · Aug 17, 2010

Exploit-DB Source

EDB-16363remotewindows✓ Verified

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

by Metasploit · Jul 3, 2010

Exploit-DB Source

EDB-40280remotewindows

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

by ohnozzy · Feb 26, 2016

Exploit-DB Source

EDB-10005doswindows✓ Verified

Microsoft Windows 7/2008 R2 - Remote Kernel Crash

by laurent gaffie · Nov 11, 2009

Exploit-DB Source

EDB-9594doswindows✓ Verified

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

by laurent gaffie · Sep 9, 2009

Exploit-DB Source

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every microsoft windows server 2008 deployment and check each version against the affected-products list above.
Remediation status
No patch has shipped for CVE-2009-3103 yet — track the microsoft windows server 2008 advisory for a fixed release and apply the workarounds below in the meantime.
Mitigate without a patch
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2009-3103 being exploited in your environment?

Detect and block the exploit chain at execution, on systems you cannot patch yet.

Protect my workloads How runtime protection works

CVE-2009-3103 — Windows Server 2008

EPSS Exploitation Probability

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

Frequently Asked Questions

Is CVE-2009-3103 being exploited in your environment?