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

> Remote attackers can bypass SecureIIS filtering via HTML escaping to perform directory traversal and access restricted files.

- **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:** 27 Jul 2001
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-473v-8xrg-7236

## What is CVE-2001-0523?

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

### Official description

eEye SecureIIS versions 1.0.3 and earlier allows a remote attacker to bypass filtering of requests made to SecureIIS by escaping HTML characters within the request, which could allow a remote attacker to use restricted variables and perform directory traversal attacks on vulnerable programs that would otherwise be protected.

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

It affects 2 products.


Products: Eeye Digital Security Secureiis, Eeye Digital Security Securells.

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

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

## Is CVE-2001-0523 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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