The Security Account Manager Remote (SAMR) protocol implementation in Microsoft Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vi…

published 2014-03-12 12y ago modified 2026-06-17 4mo ago also EUVD-2014-0355

cvss: 5.4; version 2.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 10.4%; EPSS 10.4% chance of exploitation in 30 days, percentile 95%
public exploits: 0; none known

The Security Account Manager Remote (SAMR) protocol implementation in Microsoft Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, and Windows Server 2012 Gold and R2 does not properly determine the user-lockout state, which makes it easier for remote attackers to bypass the account lockout policy and obtain access via a brute-force attack, aka "SAMR Security Feature Bypass Vulnerability."

Is CVE-2014-0317 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 Fencer

Exploit prediction

10.44% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	2.0	5.4	AV:N/AC:H/Au:N/C:N/I:C/A:N

Classification

Weakness

CWE-20 Improper Input Validation
CWE-264 Permissions, Privileges, and Access Controls

References

docs.microsoft.com /en-us/security-updates/securitybulletins/2014/ms14-016
vendor-advisory

Sources

CVE List CVE-2014-0317
NVD CVE-2014-0317

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.