# CVE-2002-0419: Information disclosure in n/a

> Remote attackers can obtain sensitive server IP, NetBIOS, and domain information via IIS authentication responses, aiding further attacks.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jun 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-3xw9-3h5v-3873

## What is CVE-2002-0419?

CVE-2002-0419 is a medium-severity vulnerability in Microsoft Internet Information Server, published on 11 Jun 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Information leaks in IIS 4 through 5.1 allow remote attackers to obtain potentially sensitive information or more easily conduct brute force attacks via responses from the server in which (2) in certain configurations, the server IP address is provided as the realm for Basic authentication, which could reveal real IP addresses that were obscured by NAT, or (3) when NTLM authentication is used, the NetBIOS name of the server and its Windows NT domain are revealed in response to an Authorization request.  NOTE: this entry originally contained a vector (1) in which the server reveals whether it supports Basic or NTLM authentication through 401 Access Denied error messages.  CVE has REJECTED this vector; it is not a vulnerability because the information is already available through legitimate use, since authentication cannot proceed without specifying a scheme that is supported by both the client and the server.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 2 products.


Products: Microsoft Internet Information Server, Microsoft Internet Information Services.

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

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

## Is CVE-2002-0419 being exploited?

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

Public exploit code:

- Microsoft IIS 4.0/5.0/5.1 - Authentication Method Disclosure (exploitdb)

## Other vulnerabilities in Microsoft Internet Information Server

- [CVE-2008-0075](https://insights.sbomify.com/CVE-2008-0075/): Code injection in n/a (critical 10.0)
- [CVE-1999-1376](https://insights.sbomify.com/CVE-1999-1376/): Buffer overflow in fpcount.exe in IIS 4.0 with FrontPage Server Extensions allows remote attackers to execute arbitrary commands. (critical 10.0)
- [CVE-1999-0407](https://insights.sbomify.com/CVE-1999-0407/): By default, IIS 4.0 has a virtual directory /IISADMPWD which contains files that can be used as proxies for brute force password attacks, or (critical 10.0)
- [CVE-1999-0874](https://insights.sbomify.com/CVE-1999-0874/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-3023](https://insights.sbomify.com/CVE-2009-3023/): Memory corruption in n/a (critical 9.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-0419 is a medium-severity vulnerability in Microsoft Internet Information Server, published on 11 Jun 2002. 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-2002-0419 exists.

Affected product: Microsoft Internet Information Server. 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-0419/ (Markdown: https://insights.sbomify.com/CVE-2002-0419/index.md)
```

## Sources

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

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