# CVE-2009-2511: Integer overflow in n/a

> Man-in-the-middle attackers can spoof SSL servers via malformed X.509 certificates exploiting an integer overflow in Windows CryptoAPI.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-f8c8-v22w-8vv8

## What is CVE-2009-2511?

CVE-2009-2511 is a high-severity vulnerability in Microsoft Windows 2000, published on 14 Oct 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Integer overflow in the CryptoAPI component in Microsoft Windows 2000 SP4, Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista Gold, SP1, and SP2, Windows Server 2008 Gold, SP2, and R2, and Windows 7 allows man-in-the-middle attackers to spoof arbitrary SSL servers and other entities via an X.509 certificate that has a malformed ASN.1 Object Identifier (OID) and was issued by a legitimate Certification Authority, aka "Integer Overflow in X.509 Object Identifiers Vulnerability."

Weakness: CWE-189

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

It affects 6 products.


Products: Microsoft Windows 2000, Microsoft Windows 7, Microsoft Windows Server 2003, Microsoft Windows Server 2008, Microsoft Windows Vista, Microsoft Windows Xp.

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

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

## Is CVE-2009-2511 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-2511 exists.

Public exploit code:

- Microsoft Internet Explorer 8 - X.509 Certificate Common Name Encoding Multiple Security Bypass Vulnerabilities (exploitdb)

## Other vulnerabilities in Microsoft Windows 2000

- [CVE-2008-4250](https://insights.sbomify.com/CVE-2008-4250/): Microsoft Windows Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2010-0232](https://insights.sbomify.com/CVE-2010-0232/): Microsoft Windows Kernel Exception Handler (high 7.8, exploited in the wild)
- [CVE-2009-1123](https://insights.sbomify.com/CVE-2009-1123/): Microsoft Windows Improper Input Validation (high 7.8, exploited in the wild)
- [CVE-2002-0367](https://insights.sbomify.com/CVE-2002-0367/): Microsoft Windows Privilege Escalation (high 7.8, exploited in the wild)
- [CVE-2010-0269](https://insights.sbomify.com/CVE-2010-0269/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-2511 is a high-severity vulnerability in Microsoft Windows 2000, published on 14 Oct 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-2511 exists.

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-2511/ (Markdown: https://insights.sbomify.com/CVE-2009-2511/index.md)
```

## Sources

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

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