How severe is CVE-2005-1983?

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

Which packages are affected by CVE-2005-1983?

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

How do I fix CVE-2005-1983?

No fixed version has been published for CVE-2005-1983 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2005-1983 actively exploited in the wild?

Yes. There are 5 known exploit references for CVE-2005-1983, including 4 documented proof-of-concept exploits on Exploit-DB and 1 in-the-wild exploitation 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-2005-1983?

CVE-2005-1983 has an EPSS (Exploit Prediction Scoring System) score of 93.0%, 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.

Which products and versions are affected by CVE-2005-1983?

CVE-2005-1983 affects microsoft windows 2000; microsoft windows xp. Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2005-1983 published, and has it been updated?

CVE-2005-1983 was published on August 10, 2005 and was last updated on April 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2005-1983

Stack-based buffer overflow in the Plug and Play (PnP) service for Microsoft Windows 2000 and Windows XP Service Pack 1 allows remote attackers to execute arbitrary code via a crafted…

Published

Aug 10, 2005

Updated

Apr 16, 2026

Affected

0 pkgs

Patched

None yet

Exploits

5 known

EPSS Exploitation Probability

via FIRST.org ↗

93.0%probability of exploitation in next 30 days

Very High Risk100th percentile+5.04%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

Stack-based buffer overflow in the Plug and Play (PnP) service for Microsoft Windows 2000 and Windows XP Service Pack 1 allows remote attackers to execute arbitrary code via a crafted packet, and local users to gain privileges via a malicious application, as exploited by the Zotob (aka Mytob) worm.

Affected Products

2 products · 2 configurations

windows 2000microsoft

all

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-16365doswindows✓ Verified

Microsoft Plug and Play Service - Overflow (MS05-039) (Metasploit)

by Metasploit · Aug 30, 2010

Exploit-DB Source

EDB-1146remotewindows✓ Verified

Microsoft Windows - Plug-and-Play Service Remote Overflow (MS05-039)

by sl0ppy · Aug 11, 2005

Exploit-DB Source

EDB-1149remotewindows✓ Verified

Microsoft Windows Plug-and-Play Service - Remote Universal (MS05-039)

by houseofdabus · Aug 12, 2005

Exploit-DB Source

EDB-1179remotewindows✓ Verified

Microsoft Windows Plug-and-Play Service - Remote Universal (Spanish) (MS05-039)

by RoMaNSoFt · Aug 25, 2005

Exploit-DB Source

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2005-1983 in your stack?

O3 detects CVE-2005-1983 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works