# CVE-2002-0020: Buffer overflow in telnet server in Windows 2000 and Interix 2.2 allows remote attackers to execute arbitrary code via malformed protocol options.


- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Jun 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-mxwp-93pm-95mr

## What is CVE-2002-0020?

CVE-2002-0020 is a high-severity vulnerability in Microsoft Windows 2000, published on 25 Jun 2002. 

### Official description

Buffer overflow in telnet server in Windows 2000 and Interix 2.2 allows remote attackers to execute arbitrary code via malformed protocol options.

## Which versions are affected by CVE-2002-0020?

It affects 2 products.


Products: Microsoft Interix, Microsoft Windows 2000.

## How do I fix CVE-2002-0020?

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

## Is CVE-2002-0020 being exploited?

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

## Other vulnerabilities in Microsoft Windows 2000

- [CVE-2004-0210](https://insights.sbomify.com/CVE-2004-0210/): Microsoft Windows Privilege Escalation (high 7.8, exploited in the wild)
- [CVE-2009-0537](https://insights.sbomify.com/CVE-2009-0537/): Integer overflow in n/a (medium 4.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-0020 and fix it if it is affected.

What it is: CVE-2002-0020 is a high-severity vulnerability in Microsoft Windows 2000, published on 25 Jun 2002. 
Exploitation: There is no known exploitation of CVE-2002-0020 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-2002-0020/ (Markdown: https://insights.sbomify.com/CVE-2002-0020/index.md)
```

## Sources

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

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