Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2017-0176: EsteemAudit: Windows Smart Card authentication buffer overflow

Published Jun 22, 2017 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.1High · v3
EPSS45.8%99th percentile
CISA KEVNoNot listed
In the wildReported3 exploitation records in Mallory
Vendor
Microsoft Corporation
IdentifiersCVE-2017-0176CWE-120 · Buffer Copy without Checking Size…

CVE-2017-0176 is a buffer overflow in the Smart Card authentication component of Microsoft Windows XP through Service Pack 3 and Windows Server 2003 through Service Pack 2. A remote attacker can exploit the vulnerability to execute arbitrary code on a target computer that is joined to a Windows domain and has Remote Desktop Protocol or Terminal Services enabled. The vulnerability is associated with the EsteemAudit exploit.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote execution of arbitrary code on an affected Windows computer. The execution privilege level and specific confidentiality, integrity, and availability consequences are not established.

Mitigation

If you can’t patch tonight, do this now.

Disable RDP or Terminal Services on affected systems where not strictly required, and restrict access to those services using network segmentation, firewall rules, VPN-only administration paths, and allowlisting of trusted management hosts. Reduce exposure of legacy domain-joined Windows XP and Server 2003 systems, monitor for anomalous RDP activity, and isolate systems that require smart card authentication support. Limiting reachability of vulnerable hosts is particularly important where patching or platform replacement is not immediately possible.

Remediation

Patch, then assume compromise.

Apply the Microsoft security update that addresses CVE-2017-0176 for affected legacy Windows platforms. Systems running Windows XP SP3 and Windows Server 2003 SP2 should be upgraded to supported operating systems where possible, as these products are end-of-life and present ongoing security risk. Remove or replace legacy hosts that cannot be patched, especially those providing RDP or Terminal Services access in domain environments.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows Server 2003operating_system
Microsoft CorporationWindows Xpoperating_system
FAQ

Frequently asked questions

Is CVE-2017-0176 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2017-0176?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2017-0176.
Is there a patch for CVE-2017-0176?
Apply the Microsoft security update that addresses CVE-2017-0176 for affected legacy Windows platforms. Systems running Windows XP SP3 and Windows Server 2003 SP2 should be upgraded to supported operating systems where possible, as these products are end-of-life and present ongoing security risk.
What products are affected by CVE-2017-0176?
Microsoft Corporation Windows Server 2003 and Microsoft Corporation Windows Xp.
How severe is CVE-2017-0176?
CVE-2017-0176 has a CVSS v3 score of 8.1 (High) and an EPSS score of 45.8% (99th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence1Every report linking this CVE to a named adversary.
Associated malware1Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.