CVE-2010-2729 in the critical feed json
The Print Spooler service in Microsoft Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista SP1 and SP2, Windows Server 2008 Gold…
published 16y ago modified 4mo ago also EUVD-2010-2733
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 75.6%
- EPSS 75.6% chance of exploitation in 30 days, percentile 99.5%
- public exploits
- 2
- Metasploit and Exploit-DB
Summary
The Print Spooler service in Microsoft Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista SP1 and SP2, Windows Server 2008 Gold, SP2, and R2, and Windows 7, when printer sharing is enabled, does not properly validate spooler access permissions, which allows remote attackers to create files in a system directory, and consequently execute arbitrary code, by sending a crafted print request over RPC, as exploited in the wild in September 2010, aka "Print Spooler Service Impersonation Vulnerability."
Is CVE-2010-2729 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (Metasploit exploit/windows/smb/ms10_061_spoolss)
- Published
Exploit prediction
75.64% chance of exploitation in the next 30 days, higher than 99.5% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/windows/smb/ms10_061_spoolss MS10-061 Microsoft Print Spooler Service Impersonation Vulnerability metasploit exploit, excellent rank, 2010-09-14
- EDB-16361 Microsoft Windows - Print Spooler Service Impersonation (MS10-061) (Metasploit) remote, 2011-02-17
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
Sources
- CVE List CVE-2010-2729
- NVD CVE-2010-2729
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.