# CVE-2007-1773: Path traversal in n/a

> Remote attackers can list arbitrary directories in aBitWhizzy via path traversal in the d parameter, exposing sensitive file structure information.

- **Severity:** Low 2.6 (`AV:N/AC:H/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:** 30 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7w84-5x2h-56hv

## What is CVE-2007-1773?

CVE-2007-1773 is a low-severity path traversal vulnerability in n/a, published on 30 Mar 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple directory traversal vulnerabilities in aBitWhizzy allow remote attackers to list arbitrary directories via a .. (dot dot) in the d parameter to (1) whizzery/whizzypic.php or (2) whizzery/whizzylink.php, different vectors than CVE-2006-6384.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2007-1773?

It affects 1 product.


Products: Unverse.net Abitwhizzy.

## How do I fix CVE-2007-1773?

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

## Is CVE-2007-1773 being exploited?

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

Public exploit code:

- aBitWhizzy - 'whizzypic.php?d' Traversal Arbitrary Directory Listing (exploitdb)
- aBitWhizzy - 'whizzylink.php?d' Traversal Arbitrary Directory Listing (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-6084](https://insights.sbomify.com/CVE-2006-6084/): Path traversal in n/a (medium 5.0)
- [CVE-2007-1774](https://insights.sbomify.com/CVE-2007-1774/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-1773 and fix it if it is affected.

What it is: CVE-2007-1773 is a low-severity path traversal vulnerability in n/a, published on 30 Mar 2007. 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-2007-1773 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-2007-1773/ (Markdown: https://insights.sbomify.com/CVE-2007-1773/index.md)
```

## Sources

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

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