How severe is CVE-2003-0352?

No CVSS score has been assigned to CVE-2003-0352 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2003-0352?

Affected package information for CVE-2003-0352 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2003-0352?

No fixed release is recorded for CVE-2003-0352 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2003-0352 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2003-0352 if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is CVE-2003-0352 actively exploited in the wild?

Yes. There are 5 known exploit references for CVE-2003-0352, including 3 documented proof-of-concept exploits on Exploit-DB and 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2003-0352?

CVE-2003-0352 has an EPSS (Exploit Prediction Scoring System) score of 98.5%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

When was CVE-2003-0352 published, and has it been updated?

CVE-2003-0352 was published on July 17, 2003 and was last updated on August 8, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Not in CISA KEV

CVE-2003-0352 — Microsoft

CVE-2003-0352 is a remote code execution vulnerability. 5 public exploit references exist, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

Buffer overflow in a certain DCOM interface for RPC in Microsoft Windows NT 4.0, 2000, XP, and Server 2003 allows remote attackers to execute arbitrary code via a malformed message,…

Published

Jul 17, 2003

Updated

Aug 8, 2024

Affected

4 products

Patched

See advisory

Exploits

5 known

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

98.5%probability of exploitation in next 30 days

Very High Risk-0.14%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

Buffer overflow in a certain DCOM interface for RPC in Microsoft Windows NT 4.0, 2000, XP, and Server 2003 allows remote attackers to execute arbitrary code via a malformed message, as exploited by the Blaster/MSblast/LovSAN and Nachi/Welchia worms.

Affected Products

4 products · 48 configurations

windows 2000microsoft

all

windows 2003 servermicrosoft

5 versions

enterpriseenterprise_64-bitr2standardweb

windows ntmicrosoft

1 version

4.0

windows xpmicrosoft

all

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-100remotewindows✓ Verified

Microsoft Windows - 'RPC DCOM' Long Filename Overflow (MS03-026)

by ey4s · Sep 16, 2003

Exploit-DB Source

EDB-22917remotewindows✓ Verified

Microsoft Windows - DCOM RPC Interface Buffer Overrun

by [email protected] · Aug 11, 2003

Exploit-DB Source

EDB-16749remotewindows✓ Verified

Microsoft RPC DCOM Interface - Remote Overflow (MS03-026) (Metasploit)

by Metasploit · Jan 11, 2011

Exploit-DB Source

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2003-0352 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2003-0352 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2003-0352 — Microsoft

EPSS Exploitation Probability

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

Frequently Asked Questions

Is CVE-2003-0352 in your dependencies?