# CVE-2010-0269: Memory corruption in n/a

> Remote attackers can execute arbitrary code on Windows systems by sending crafted SMB responses to the client.

- **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:** 14 Apr 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-65m6-pr6v-g87w

## What is CVE-2010-0269?

CVE-2010-0269 is a critical memory corruption vulnerability in Microsoft Windows 2000, published on 14 Apr 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The SMB client in Microsoft Windows 2000 SP4, Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista Gold, SP1, and SP2, Windows Server 2008 Gold, SP2, and R2, and Windows 7 does not properly allocate memory for SMB responses, which allows remote SMB servers and man-in-the-middle attackers to execute arbitrary code via a crafted (1) SMBv1 or (2) SMBv2 response, aka "SMB Client Memory Allocation Vulnerability."

Weakness: CWE-399

## Which versions are affected by CVE-2010-0269?

It affects 7 products.


Products: Microsoft Windows 2000, Microsoft Windows 2003 Server, Microsoft Windows 7, Microsoft Windows Server 2003, Microsoft Windows Server 2008, Microsoft Windows Vista, Microsoft Windows Xp.

## How do I fix CVE-2010-0269?

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

## Is CVE-2010-0269 being exploited?

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

Public exploit code:

- Microsoft Windows 7/2008 R2 - SMB Client Trans2 Stack Overflow (MS10-020) (PoC) (exploitdb)

## Other vulnerabilities in Microsoft Windows 2000

- [CVE-2008-4250](https://insights.sbomify.com/CVE-2008-4250/): Microsoft Windows Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2010-0232](https://insights.sbomify.com/CVE-2010-0232/): Microsoft Windows Kernel Exception Handler (high 7.8, exploited in the wild)
- [CVE-2009-1123](https://insights.sbomify.com/CVE-2009-1123/): Microsoft Windows Improper Input Validation (high 7.8, exploited in the wild)
- [CVE-2002-0367](https://insights.sbomify.com/CVE-2002-0367/): Microsoft Windows Privilege Escalation (high 7.8, exploited in the wild)
- [CVE-2010-0231](https://insights.sbomify.com/CVE-2010-0231/): Weak cryptography in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-0269 and fix it if it is affected.

What it is: CVE-2010-0269 is a critical memory corruption vulnerability in Microsoft Windows 2000, published on 14 Apr 2010. 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-2010-0269 exists.

Affected product: Microsoft Windows 2000. 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-2010-0269/ (Markdown: https://insights.sbomify.com/CVE-2010-0269/index.md)
```

## Sources

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

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