# CVE-2009-1139: Denial of service in n/a

> Remote attackers can cause denial of service in Active Directory LDAP services via crafted OID filters, requiring patches for Windows servers.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jun 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-w4vc-26qw-m4wv

## What is CVE-2009-1139?

CVE-2009-1139 is a high-severity denial of service vulnerability in Microsoft Windows 2000, published on 10 Jun 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Memory leak in the LDAP service in Active Directory on Microsoft Windows 2000 SP4 and Server 2003 SP2, and Active Directory Application Mode (ADAM) on Windows XP SP2 and SP3 and Server 2003 SP2, allows remote attackers to cause a denial of service (memory consumption and service outage) via (1) LDAP or (2) LDAPS requests with unspecified OID filters, aka "Active Directory Memory Leak Vulnerability."

Weakness: CWE-399

## Which versions are affected by CVE-2009-1139?

It affects 3 products.


Products: Microsoft Adam, Microsoft Windows 2000, Microsoft Windows Server 2003.

## How do I fix CVE-2009-1139?

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

## Is CVE-2009-1139 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-1139 and fix it if it is affected.

What it is: CVE-2009-1139 is a high-severity denial of service vulnerability in Microsoft Windows 2000, published on 10 Jun 2009. 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-2009-1139 in the wild and no public exploit code.

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

## Sources

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

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