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

> Remote attackers can determine the web root path via a direct request to a specific servlet, leaking sensitive pathname information in error messages.

- **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:** 2 Apr 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-2xh5-xf3c-xgfw

## What is CVE-2002-0892?

CVE-2002-0892 is a medium-severity vulnerability in n/a, published on 2 Apr 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The default configuration of NewAtlanta ServletExec ISAPI 4.1 allows remote attackers to determine the path of the web root via a direct request to com.newatlanta.servletexec.JSP10Servlet without a filename, which leaks the pathname in an error message.

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

It affects 1 product.


Products: New Atlanta Communications Servletexec Isapi.

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

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

## Is CVE-2002-0892 being exploited?

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

Public exploit code:

- NewAtlanta ServletExec/ISAPI 4.1 - Full Path Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2002-0893](https://insights.sbomify.com/CVE-2002-0893/): Path traversal in n/a (medium 5.0)
- [CVE-2002-0894](https://insights.sbomify.com/CVE-2002-0894/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-0892 is a medium-severity vulnerability in n/a, published on 2 Apr 2003. 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-0892 exists.

Affected product: n/a. 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-0892/ (Markdown: https://insights.sbomify.com/CVE-2002-0892/index.md)
```

## Sources

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

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