# CVE-2003-1166: Path traversal in n/a

> Remote attackers can view arbitrary files via directory traversal in HTTP Commander web application.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 May 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-3fp6-x3rc-h83r

## What is CVE-2003-1166?

CVE-2003-1166 is a medium-severity path traversal vulnerability in n/a, published on 10 May 2005. It can be exploited over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in (1) Openfile.aspx and (2) Html.aspx in HTTP Commander 4.0 allows remote attackers to view arbitrary files via a .. (dot dot) in the file parameter.

## Which versions are affected by CVE-2003-1166?

It affects 1 product.


Products: Http Commander Http Commander.

## How do I fix CVE-2003-1166?

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

## Is CVE-2003-1166 being exploited?

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

Public exploit code:

- http commander 4.0 - Directory Traversal (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-0583](https://insights.sbomify.com/CVE-2007-0583/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-1166 and fix it if it is affected.

What it is: CVE-2003-1166 is a medium-severity path traversal vulnerability in n/a, published on 10 May 2005. It can be exploited over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-1166 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-2003-1166/ (Markdown: https://insights.sbomify.com/CVE-2003-1166/index.md)
```

## Sources

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

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