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

> Remote attackers can execute arbitrary code on Windows systems via malformed RPC responses due to improper memory allocation in the RPC client.

- **Severity:** Critical 9.3 (`AV:N/AC:M/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:** 15 Sep 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-w379-57qr-347p

## What is CVE-2010-2567?

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

### Official description

The RPC client implementation in Microsoft Windows XP SP2 and SP3 and Server 2003 SP2 does not properly allocate memory during the parsing of responses, which allows remote RPC servers and man-in-the-middle attackers to execute arbitrary code via a malformed response, aka "RPC Memory Corruption Vulnerability."

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 2 products.


Products: Microsoft Windows Server 2003, Microsoft Windows Xp.

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

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

## Is CVE-2010-2567 being exploited?

There is no known exploitation of CVE-2010-2567 in the wild and no public exploit code.

## Other vulnerabilities in Microsoft Windows Server 2003

- [CVE-2011-2005](https://insights.sbomify.com/CVE-2011-2005/): Microsoft Ancillary Function Driver (afd.sys) Improper Input Validation (high 7.8, exploited in the wild)
- [CVE-2013-3863](https://insights.sbomify.com/CVE-2013-3863/): Memory corruption in n/a (critical 9.3)
- [CVE-2013-3181](https://insights.sbomify.com/CVE-2013-3181/): Memory corruption in n/a (critical 9.3)
- [CVE-2013-0077](https://insights.sbomify.com/CVE-2013-0077/): Code injection in n/a (critical 9.3)
- [CVE-2012-0009](https://insights.sbomify.com/CVE-2012-0009/): Path traversal in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-2567 is a critical memory corruption vulnerability in Microsoft Windows Server 2003, published on 15 Sep 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-2567 in the wild and no public exploit code.

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

## Sources

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

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