# CVE-2001-0276: Information disclosure in n/a

> Remote attackers can determine the server's physical path by calling ext.dll without arguments, revealing sensitive directory information.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Mar 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-v5fv-q4p8-9g5q

## What is CVE-2001-0276?

CVE-2001-0276 is a medium-severity vulnerability in n/a, published on 9 Mar 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ext.dll in BadBlue 1.02.07 Personal Edition web server allows remote attackers to determine the physical path of the server by directly calling ext.dll without any arguments, which produces an error message that contains the path.

## Which versions are affected by CVE-2001-0276?

It affects 1 product.


Products: Working Resources Inc. Badblue.

## How do I fix CVE-2001-0276?

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

## Is CVE-2001-0276 being exploited?

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

Public exploit code:

- Working Resources BadBlue 1.2.7 - Full Path Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2001-0277](https://insights.sbomify.com/CVE-2001-0277/): Memory corruption in n/a (critical 10.0)
- [CVE-2003-0332](https://insights.sbomify.com/CVE-2003-0332/): Auth bypass in n/a (high 7.6)
- [CVE-2002-2170](https://insights.sbomify.com/CVE-2002-2170/): Missing authorization in n/a (high 7.5)
- [CVE-2005-0595](https://insights.sbomify.com/CVE-2005-0595/): Memory corruption in n/a (high 7.5)
- [CVE-2002-1541](https://insights.sbomify.com/CVE-2002-1541/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-0276 and fix it if it is affected.

What it is: CVE-2001-0276 is a medium-severity vulnerability in n/a, published on 9 Mar 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-2001-0276 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-2001-0276/ (Markdown: https://insights.sbomify.com/CVE-2001-0276/index.md)
```

## Sources

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

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