LiveActive security incident?Get immediate response
CVE Record

CVE-2003-0605: The RPC DCOM interface in Windows 2000 SP3 and SP4 allows remote attackers to cause a denial of service (cr...

The RPC DCOM interface in Windows 2000 SP3 and SP4 allows remote attackers to cause a denial of service (crash), and local attackers to use the DoS to hijack the epmapper pipe to gain privileges, via certain messages to the __RemoteGetClassObject interface that cause a NULL pointer to be passed to the PerformScmStage function.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This is an old Windows 2000 RPC DCOM flaw. A remote attacker could crash affected systems, and a local attacker could potentially use the resulting condition to gain higher privileges. Exposure should be treated as legacy-system risk, especially where Windows 2000 SP3 or SP4 remains connected to business networks. Likely exposure is limited to Windows 2000 SP3 and SP4 systems using the affected RPC DCOM interface. The supplied affected-products metadata is incomplete, so asset validation should rely on operating system inventory, vendor advisory review, and OVAL checks where available. Prioritize remediation where Windows 2000 systems support production, identity, manufacturing, or remote-access functions. Business urgency is highest when RPC/DCOM is reachable from untrusted networks or when local users can access the host. If no affected systems exist, document the exception and close as not applicable. Mitigation focus: Identify any Windows 2000 SP3 or SP4 systems still operating.; Review and apply Microsoft guidance in MS03-039 for affected systems.; Isolate or decommission legacy systems that cannot follow vendor guidance..

Prepared

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-0605 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
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
4Source links

CVSS and timeline data

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

Source materials

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.