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

> Remote attackers can execute arbitrary commands via directory traversal in Jetty's CGIServlet, requiring an upgrade to secure the server.

- **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:** No
- **Published:** 1 Sep 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-rrv3-c2mh-pf7x

## What is CVE-2002-1178?

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

### Official description

Directory traversal vulnerability in the CGIServlet for Jetty HTTP server before 4.1.0 allows remote attackers to execute arbitrary commands via ..\ (dot-dot backslash) sequences in an HTTP request to the cgi-bin directory.

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

It affects 1 product.


Products: Jetty Jetty Http Server.

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

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

## Is CVE-2002-1178 being exploited?

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

Public exploit code:

- Jetty 3.1.6/3.1.7/4.1 Servlet Engine - Arbitrary Command Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-6969](https://insights.sbomify.com/CVE-2006-6969/): Jetty Uses Predictable Session Identifiers (medium 6.8)
- [CVE-2004-2381](https://insights.sbomify.com/CVE-2004-2381/): Jetty HTTP Server Denial of Service vulnerability (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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