# CVE-2013-3868: Denial of service in n/a

> Remote attackers can cause a denial of service in Microsoft Active Directory Lightweight Directory Services via a crafted LDAP query.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/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:** 11 Sep 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vj9r-5x9p-j6m6

## What is CVE-2013-3868?

CVE-2013-3868 is a medium-severity denial of service vulnerability in Microsoft Windows 7, published on 11 Sep 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Microsoft Active Directory Lightweight Directory Service (AD LDS) on Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, and Windows 8 and Active Directory Services on Windows Server 2008 SP2 and R2 SP1 and Server 2012 allow remote attackers to cause a denial of service (LDAP directory-service outage) via a crafted LDAP query, aka "Remote Anonymous DoS Vulnerability."

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2013-3868?

It affects 6 products.


Products: Microsoft Active Directory Lightweight Directory Service, Microsoft Windows 7, Microsoft Windows 8, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Vista.

## How do I fix CVE-2013-3868?

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

## Is CVE-2013-3868 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-3868 and fix it if it is affected.

What it is: CVE-2013-3868 is a medium-severity denial of service vulnerability in Microsoft Windows 7, published on 11 Sep 2013. 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-2013-3868 in the wild and no public exploit code.

Affected product: Microsoft Windows 7. 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-2013-3868/ (Markdown: https://insights.sbomify.com/CVE-2013-3868/index.md)
```

## Sources

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

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