# CVE-2002-1562: Path traversal in n/a

> Remote attackers can read arbitrary files via directory traversal in the Host header when virtual hosting is enabled.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Apr 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-wq97-jr7v-qwxf

## What is CVE-2002-1562?

CVE-2002-1562 is a medium-severity path traversal vulnerability in n/a, published on 26 Apr 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in thttpd, when using virtual hosting, allows remote attackers to read arbitrary files via .. (dot dot) sequences in the Host: header.

## Which versions are affected by CVE-2002-1562?

It affects 1 product.


Products: Acme Labs Thttpd.

## How do I fix CVE-2002-1562?

Upgrade to a fixed version.

## Is CVE-2002-1562 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2000-0359](https://insights.sbomify.com/CVE-2000-0359/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-1078](https://insights.sbomify.com/CVE-2006-1078/): Memory corruption in n/a (high 8.4)
- [CVE-2002-0733](https://insights.sbomify.com/CVE-2002-0733/): Cross-site scripting in n/a (high 7.5)
- [CVE-2000-0900](https://insights.sbomify.com/CVE-2000-0900/): Path traversal in n/a (high 7.5)
- [CVE-2006-4248](https://insights.sbomify.com/CVE-2006-4248/): Path traversal in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-1562 and fix it if it is affected.

What it is: CVE-2002-1562 is a medium-severity path traversal vulnerability in n/a, published on 26 Apr 2003. 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-2002-1562 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-2002-1562/ (Markdown: https://insights.sbomify.com/CVE-2002-1562/index.md)
```

## Sources

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

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