# CVE-2001-1138: Path traversal in n/a

> Remote attackers can read arbitrary files and potentially execute code via directory traversal in the FILE parameter of Power Up HTML.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/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:** 15 Mar 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-37mh-6cwh-pwc5

## What is CVE-2001-1138?

CVE-2001-1138 is a high-severity path traversal vulnerability in n/a, published on 15 Mar 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in r.pl (aka r.cgi) of Randy Parker Power Up HTML 0.8033beta allows remote attackers to read arbitrary files and possibly execute arbitrary code via a .. (dot dot) in the FILE parameter.

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

It affects 1 product.


Products: Randy Parker Power Up Html.

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

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

## Is CVE-2001-1138 being exploited?

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

Public exploit code:

- Power Up HTML 0.8033 Beta - Directory Traversal Arbitrary File Disclosure (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2001-1138 is a high-severity path traversal vulnerability in n/a, published on 15 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-1138 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-1138/ (Markdown: https://insights.sbomify.com/CVE-2001-1138/index.md)
```

## Sources

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

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