CVE-2017-0176 in the critical feed json
A buffer overflow in Smart Card authentication code in gpkcsp.dll in Microsoft Windows XP through SP3 and Server 2003 through SP2 allows a…
published 2017-06-22 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-0543
- cvss
- 8.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 45.8%
- EPSS 45.8% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known
Summary
A buffer overflow in Smart Card authentication code in gpkcsp.dll in Microsoft Windows XP through SP3 and Server 2003 through SP2 allows a remote attacker to execute arbitrary code on the target computer, provided that the computer is joined in a Windows domain and has Remote Desktop Protocol connectivity (or Terminal Services) enabled.
Patch / fix
Exploit prediction
45.77% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- blog.fortinet.com https://blog.fortinet.com/2017/05/11/deep-analysis-of-esteemaudit referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.1 | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Affected products
- Microsoft Microsoft Windows Server 2003 SP1, SP2 Windows XP - SP3
Classification
- Weakness
-
- CWE-120 Buffer Copy without Checking Size of Input
References
-
support.microsoft.com
/en-us/help/4022747/security-update-for-windows-xp-and-windows-server-2003
patch, vendor-advisory
-
blogs.technet.microsoft.com
/msrc/2017/04/14/protecting-customers-and-evaluating-risk/
patch, vendor-advisory
-
blog.fortinet.com
/2017/05/11/deep-analysis-of-esteemaudit
exploit, third-party-advisory
-
securityfocus.com
/bid/98550
vdb-entry, third-party-advisory
-
securityfocus.com
/bid/98752
vdb-entry, third-party-advisory
- blog.0patch.com /2017/06/a-quick-analysis-of-microsofts.html
Sources
- CVE List CVE-2017-0176
- NVD CVE-2017-0176
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.