# CVE-2006-2633: Path traversal in n/a

> Authenticated attackers can exploit path traversal in ByteHoard to create or overwrite files in other users' directories via crafted parameters.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-c64v-q593-c6mp

## What is CVE-2006-2633?

CVE-2006-2633 is a medium-severity path traversal vulnerability in n/a, published on 30 May 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Absolute path traversal vulnerability in the copy action in index.php in Andrew Godwin ByteHoard 2.1 and earlier allows remote authenticated users to create or overwrite files in other users' directories by specifying the absolute path of the directory in the infolder parameter and simultaneously specifying the filename in the filepath parameter.

## Which versions are affected by CVE-2006-2633?

It affects 1 product.


Products: Andrew Godwin Bytehoard.

## How do I fix CVE-2006-2633?

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

## Is CVE-2006-2633 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-2849](https://insights.sbomify.com/CVE-2006-2849/): Code injection in n/a (high 7.5)
- [CVE-2006-2632](https://insights.sbomify.com/CVE-2006-2632/): Cross-site scripting in n/a (low 3.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-2633 and fix it if it is affected.

What it is: CVE-2006-2633 is a medium-severity path traversal vulnerability in n/a, published on 30 May 2006. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-2633 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-2006-2633/ (Markdown: https://insights.sbomify.com/CVE-2006-2633/index.md)
```

## Sources

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

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