# CVE-1999-1437: Path traversal in n/a

> Remote attackers can read arbitrary files and potentially execute commands via path traversal in ePerl's bar.phtml script.

- **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:** 9 Mar 2002
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-74xc-6hpg-hp8m

## What is CVE-1999-1437?

CVE-1999-1437 is a high-severity path traversal 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

ePerl 2.2.12 allows remote attackers to read arbitrary files and possibly execute certain commands by specifying a full pathname of the target file as an argument to bar.phtml.

## Which versions are affected by CVE-1999-1437?

It affects 1 product.


Products: Ralf S. Engelschall Eperl.

## How do I fix CVE-1999-1437?

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

## Is CVE-1999-1437 being exploited?

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

Public exploit code:

- Ralf S. Engelschall ePerl 2.2.12 - Handling of ISINDEX Query (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2001-0733](https://insights.sbomify.com/CVE-2001-0733/): Code injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-1999-1437 and fix it if it is affected.

What it is: CVE-1999-1437 is a high-severity path traversal 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-1999-1437 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-1999-1437/ (Markdown: https://insights.sbomify.com/CVE-1999-1437/index.md)
```

## Sources

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

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