# CVE-2003-0813: Race condition in n/a

> Remote attackers can cause a denial of service in Windows RPC DCOM by triggering a race condition that leads to use-after-free, requiring the MS03-039 patch.

- **Severity:** Medium 5.1 (`AV:N/AC:H/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2003
- **Updated:** 8 Aug 2024
- **Also known as:** CVE-2003-0862, GHSA-5f25-6f2x-h9x6

## What is CVE-2003-0813?

CVE-2003-0813 is a medium-severity vulnerability in Microsoft Windows 2000, published on 15 Oct 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A multi-threaded race condition in the Windows RPC DCOM functionality with the MS03-039 patch installed allows remote attackers to cause a denial of service (crash or reboot) by causing two threads to process the same RPC request, which causes one thread to use memory after it has been freed, a different vulnerability than CVE-2003-0352 (Blaster/Nachi), CVE-2003-0715, and CVE-2003-0528, and as demonstrated by certain exploits against those vulnerabilities.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

## Which versions are affected by CVE-2003-0813?

It affects 5 products.


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

## How do I fix CVE-2003-0813?

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

## Is CVE-2003-0813 being exploited?

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

## 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-2003-0813 and fix it if it is affected.

What it is: CVE-2003-0813 is a medium-severity vulnerability in Microsoft Windows 2000, published on 15 Oct 2003. 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-2003-0813 in the wild and no public exploit code.

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-2003-0813/ (Markdown: https://insights.sbomify.com/CVE-2003-0813/index.md)
```

## Sources

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

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