# CVE-2008-4250: Microsoft Windows Buffer Overflow

> Remote attackers can execute arbitrary code on Windows systems via a crafted RPC request triggering a buffer overflow in the Server service.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 20 May 2026 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Oct 2008
- **Updated:** 21 May 2026
- **Also known as:** GHSA-3v68-r58v-m4c2

## What is CVE-2008-4250?

CVE-2008-4250 is a critical memory corruption vulnerability in Microsoft Windows 2000, published on 23 Oct 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Server service in Microsoft Windows 2000 SP4, XP SP2 and SP3, Server 2003 SP1 and SP2, Vista Gold and SP1, Server 2008, and 7 Pre-Beta allows remote attackers to execute arbitrary code via a crafted RPC request that triggers the overflow during path canonicalization, as exploited in the wild by Gimmiv.A in October 2008, aka "Server Service Vulnerability."

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2008-4250?

It affects 5 products.


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

## How do I fix CVE-2008-4250?

No fix has been published for CVE-2008-4250 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 Jun 2026.

## Is CVE-2008-4250 being exploited?

Yes. Attackers have exploited CVE-2008-4250 in the wild since at least 20 May 2026.

Public exploit code:

- This repository contains some python scripts implementation for the MS08-067 Windows Server Service vulnerability (CVE-2008-4250). This is a classic remote code execution vulnerability affecting older Windows systems. (github_poc): https://github.com/BinRacer/ms08-067.py
- Scripts to analyze conflicker worm which exploits famous netapi vulnerability (CVE-2008-4250) i.e MS08-067 (github_poc): https://github.com/thunderstrike9090/Conflicker_analysis_scripts
- MS08-067 | CVE-2008-4250 (github_poc): https://github.com/NoTrustedx/Exploit_MS08-067
- Microsoft Windows Server - Code Execution (PoC) (MS08-067) (exploitdb)
- Microsoft Windows Server - Universal Code Execution (MS08-067) (exploitdb)
- MS08-067 Microsoft Server Service Relative Path Stack Corruption (metasploit)

## Other vulnerabilities in Microsoft Windows 2000

- [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)
- [CVE-2010-0231](https://insights.sbomify.com/CVE-2010-0231/): Weak cryptography in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-4250 and fix it if it is affected.

What it is: CVE-2008-4250 is a critical memory corruption vulnerability in Microsoft Windows 2000, published on 23 Oct 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2008-4250 in the wild since at least 20 May 2026.

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

## Sources

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

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