CVE-2003-0813: n/a vulnerability

CVE-2003-0813: A multi-threaded race condition in the Windows RPC DCOM functionality with the MS03-039 patch installed all...

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.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 8, 2024, 02:05 UTC (UTC+00:00)

Security readout for executives and security teams

CVE-2003-0813 is a denial-of-service flaw in Windows RPC DCOM after the MS03-039 patch. A remote attacker could trigger a race condition that crashes or reboots the system. The provided sources do not establish current active exploitation or list exact affected versions. Exposure is most likely limited to legacy Windows systems with RPC DCOM functionality and the MS03-039 patch installed. Exact affected platforms are not enumerated in the bundle, so asset validation should rely on Microsoft MS04-012, CERT, and OVAL checks. Prioritize if the organization still operates legacy Windows systems or exposes RPC/DCOM internally or externally. For modern fully patched environments, urgency is likely lower, but legacy systems can face outage risk from remote crashes. Mitigation focus: Review and apply Microsoft MS04-012 guidance for affected systems.; Identify legacy Windows hosts still exposing RPC/DCOM services.; Restrict RPC/DCOM exposure from untrusted networks where operationally possible..

Prepared: Jun 30, 2026, 08:14 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2003-0813 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Oct 15, 2003, 04:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
oval:org.mitre.oval:def:894CVE reference · vdb-entry, signature
MS04-012CVE reference · vendor-advisory, x_refsource_MS
oval:org.mitre.oval:def:900CVE reference · vdb-entry, signature
oval:org.mitre.oval:def:893CVE reference · vdb-entry, signature

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.