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

> Remote attackers can determine the full web root path by analyzing error responses to crafted GET requests, exposing internal directory structures.

- **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:** 5 Aug 2005
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-w2f9-gh9j-c75f

## What is CVE-2002-2094?

CVE-2002-2094 is a medium-severity vulnerability in n/a, published on 5 Aug 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Joe Testa hellbent 01 allows remote attackers to determine the full path of the web root directory via a GET request with a relative path that includes the root's parent, which generates a 403 error message if the parent is incorrect, but a normal response if the parent is correct.

Weakness: CWE-203 (Observable Discrepancy)

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

It affects 1 product.


Products: Joetesta Hellbent.

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

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

## Is CVE-2002-2094 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2002-2094 is a medium-severity vulnerability in n/a, published on 5 Aug 2005. 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-2002-2094 in the wild and no public exploit code.

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

## Sources

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

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