# CVE-2014-0317: Security feature bypass in n/a

> Remote attackers can bypass account lockout policies via the SAMR protocol to facilitate brute-force attacks and gain unauthorized access.

- **Severity:** Medium 5.4 (`AV:N/AC:H/Au:N/C:N/I:C/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Mar 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vcff-c2p6-3gcj

## What is CVE-2014-0317?

CVE-2014-0317 is a medium-severity vulnerability in Microsoft Windows Server 2003, published on 12 Mar 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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."

Weakness: CWE-264, CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2014-0317?

It affects 5 products.


Products: Microsoft Windows Server 2003, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Vista, Microsoft Windows Xp.

## How do I fix CVE-2014-0317?

No fix has been published for CVE-2014-0317 yet. Limit exposure of the affected software until one is available.

## Is CVE-2014-0317 being exploited?

There is no known exploitation of CVE-2014-0317 in the wild and no public exploit code.

## Other vulnerabilities in Microsoft Windows Server 2003

- [CVE-2011-2005](https://insights.sbomify.com/CVE-2011-2005/): Microsoft Ancillary Function Driver (afd.sys) Improper Input Validation (high 7.8, exploited in the wild)
- [CVE-2013-3863](https://insights.sbomify.com/CVE-2013-3863/): Memory corruption in n/a (critical 9.3)
- [CVE-2013-3181](https://insights.sbomify.com/CVE-2013-3181/): Memory corruption in n/a (critical 9.3)
- [CVE-2013-0077](https://insights.sbomify.com/CVE-2013-0077/): Code injection in n/a (critical 9.3)
- [CVE-2012-0009](https://insights.sbomify.com/CVE-2012-0009/): Path traversal in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-0317 and fix it if it is affected.

What it is: CVE-2014-0317 is a medium-severity vulnerability in Microsoft Windows Server 2003, published on 12 Mar 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-0317 in the wild and no public exploit code.

Affected product: Microsoft Windows Server 2003. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2014-0317/ (Markdown: https://insights.sbomify.com/CVE-2014-0317/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-0317
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-0317
- OSV: https://osv.dev/vulnerability/CVE-2014-0317

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-0317/
Summaries are generated and may contain mistakes; the official description above is the record.