# CVE-2009-2505: Memory corruption in n/a

> Remote attackers can execute arbitrary code on Windows Vista and Server 2008 by sending malformed MS-CHAP v2 PEAP authentication requests to the Internet Authentication Service.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/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:** 9 Dec 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3vqg-cv53-whw6

## What is CVE-2009-2505?

CVE-2009-2505 is a critical memory corruption vulnerability in Microsoft Windows Server 2008, published on 9 Dec 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Internet Authentication Service (IAS) in Microsoft Windows Vista SP2 and Server 2008 SP2 does not properly validate MS-CHAP v2 Protected Extensible Authentication Protocol (PEAP) authentication requests, which allows remote attackers to execute arbitrary code via crafted structures in a malformed request, aka "Internet Authentication Service Memory Corruption Vulnerability."

Weakness: CWE-287 (Improper Authentication)

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

It affects 2 products.


Products: Microsoft Windows Server 2008, Microsoft Windows Vista.

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

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

## Is CVE-2009-2505 being exploited?

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

## Other vulnerabilities in Microsoft Windows Server 2008

- [CVE-2020-1350](https://insights.sbomify.com/CVE-2020-1350/): Microsoft Windows DNS Server Remote Code Execution (critical 10.0, exploited in the wild)
- [CVE-2020-1040](https://insights.sbomify.com/CVE-2020-1040/): Microsoft Hyper-V RemoteFX vGPU Remote Code Execution (critical 9.0, exploited in the wild)
- [CVE-2011-1966](https://insights.sbomify.com/CVE-2011-1966/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-0239](https://insights.sbomify.com/CVE-2010-0239/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-0240](https://insights.sbomify.com/CVE-2010-0240/): Code injection in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-2505 is a critical memory corruption vulnerability in Microsoft Windows Server 2008, published on 9 Dec 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-2505 in the wild and no public exploit code.

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

## Sources

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

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