# CVE-2005-2119: Memory corruption in n/a

> Attackers can execute arbitrary code by exploiting a memory corruption vulnerability in the Microsoft Distributed Transaction Coordinator proxy.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Oct 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-jmff-53w8-2jwr

## What is CVE-2005-2119?

CVE-2005-2119 is a medium-severity memory corruption vulnerability in Microsoft Windows 2000, published on 11 Oct 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The MIDL_user_allocate function in the Microsoft Distributed Transaction Coordinator (MSDTC) proxy (MSDTCPRX.DLL) allocates a 4K page of memory regardless of the required size, which allows attackers to overwrite arbitrary memory locations using an incorrect size value that is provided to the NdrAllocate function, which writes management data to memory outside of the allocated buffer.

## Which versions are affected by CVE-2005-2119?

It affects 3 products.


Products: Microsoft Windows 2000, Microsoft Windows 2003 Server, Microsoft Windows Xp.

## How do I fix CVE-2005-2119?

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

## Is CVE-2005-2119 being exploited?

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

Public exploit code:

- Microsoft Windows - MSDTC Service Remote Memory Modification (PoC) (MS05-051) (exploitdb)
- Microsoft Windows - DTC Remote (MS05-051) (2) (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-0269](https://insights.sbomify.com/CVE-2010-0269/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2119 and fix it if it is affected.

What it is: CVE-2005-2119 is a medium-severity memory corruption vulnerability in Microsoft Windows 2000, published on 11 Oct 2005. 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-2005-2119 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-2005-2119/ (Markdown: https://insights.sbomify.com/CVE-2005-2119/index.md)
```

## Sources

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

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