# CVE-2009-3103: Memory corruption in n/a

> Remote attackers can execute arbitrary code or crash the system via a malformed SMBv2 packet, affecting Windows Vista, Server 2008, and 7.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Sep 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-47wf-g7rm-46qq

## What is CVE-2009-3103?

CVE-2009-3103 is a critical memory corruption vulnerability in Microsoft Windows Server 2008, published on 8 Sep 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-399

## Which versions are affected by CVE-2009-3103?

It affects 2 products.


Products: Microsoft Windows Server 2008, Microsoft Windows Vista.

## How do I fix CVE-2009-3103?

No fix has been published for CVE-2009-3103 yet. Limit exposure of the affected software until one is available.

## Is CVE-2009-3103 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-3103 exists.

Public exploit code:

- Microsoft Windows - 'srv2.sys' SMB Code Execution (Python) (MS09-050) (github_poc): https://github.com/Sic4rio/CVE-2009-3103---srv2.sys-SMB-Code-Execution-Python-MS09-050-
- cve-2009-3103 (github_poc): https://github.com/sooklalad/ms09050
- MS09-050 Microsoft SRV2.SYS SMB Negotiate ProcessID Function Table Dereference (metasploit)
- Microsoft Windows Vista/7 - SMB2.0 Negotiate Protocol Request Remote Blue Screen of Death (MS07-063) (exploitdb)
- Microsoft Windows 7/2008 R2 - Remote Kernel Crash (exploitdb)
- Microsoft Windows - SMB2 Negotiate Protocol '0x72' Response Denial of Service (exploitdb)

## Other vulnerabilities in Microsoft Windows Server 2008

- [CVE-2020-1350](https://insights.sbomify.com/CVE-2020-1350/): Microsoft Windows DNS Server Remote Code Execution (critical 10.0, exploited in the wild)
- [CVE-2020-1040](https://insights.sbomify.com/CVE-2020-1040/): Microsoft Hyper-V RemoteFX vGPU Remote Code Execution (critical 9.0, exploited in the wild)
- [CVE-2011-1966](https://insights.sbomify.com/CVE-2011-1966/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-0239](https://insights.sbomify.com/CVE-2010-0239/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-0240](https://insights.sbomify.com/CVE-2010-0240/): Code injection in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-3103 and fix it if it is affected.

What it is: CVE-2009-3103 is a critical memory corruption vulnerability in Microsoft Windows Server 2008, published on 8 Sep 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-3103 exists.

Affected product: Microsoft Windows Server 2008. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2009-3103/ (Markdown: https://insights.sbomify.com/CVE-2009-3103/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2009-3103
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2009-3103
- OSV: https://osv.dev/vulnerability/CVE-2009-3103

---
From sbomify Insights: https://insights.sbomify.com/CVE-2009-3103/
Summaries are generated and may contain mistakes; the official description above is the record.