# CVE-2004-0696: Path traversal in n/a

> Remote attackers can list arbitrary directories on 4D WebSTAR servers via crafted URLs, exposing sensitive file structure information.

- **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:** 16 Jul 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-hpfw-83fw-cc3h

## What is CVE-2004-0696?

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

### Official description

The ShellExample.cgi script in 4D WebSTAR 5.3.2 and earlier allows remote attackers to list arbitrary directories via a URL with the desired path and a "*" (asterisk) character.

## Which versions are affected by CVE-2004-0696?

It affects 1 product.


Products: 4d Webstar.

## How do I fix CVE-2004-0696?

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

## Is CVE-2004-0696 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-0695](https://insights.sbomify.com/CVE-2004-0695/): Memory corruption in n/a (high 7.5)
- [CVE-2004-0079](https://insights.sbomify.com/CVE-2004-0079/): Null dereference in n/a (high 7.5)
- [CVE-2005-3143](https://insights.sbomify.com/CVE-2005-3143/): Denial of service in n/a (medium 5.0)
- [CVE-2005-1507](https://insights.sbomify.com/CVE-2005-1507/): Memory corruption in n/a (medium 5.0)
- [CVE-2004-0697](https://insights.sbomify.com/CVE-2004-0697/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-0696 and fix it if it is affected.

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

## Sources

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

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