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

> Remote attackers can include arbitrary files via the appserv_root parameter in AppServ, potentially leading to data exposure or code execution.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jan 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xc9w-c2g3-64r6

## What is CVE-2006-0125?

CVE-2006-0125 is a medium-severity path traversal vulnerability in n/a, published on 9 Jan 2006. It can be exploited over the network, with no action from the victim.

### Official description

Unspecified vulnerability in appserv/main.php in AppServ 2.4.5 allows remote attackers to include arbitrary files via the appserv_root parameter.  NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.  There is not enough detail from these third party sources to know whether this is directory traversal, remote file include, or another issue.

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

It affects 1 product.


Products: Appserv Open Project Appserv.

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

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

## Is CVE-2006-0125 being exploited?

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

Public exploit code:

- AppServ Open Project 2.4.5 - Remote File Inclusion (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2004-1532](https://insights.sbomify.com/CVE-2004-1532/): Hardcoded credentials in n/a (high 7.5)
- [CVE-2008-2398](https://insights.sbomify.com/CVE-2008-2398/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-0125 is a medium-severity path traversal vulnerability in n/a, published on 9 Jan 2006. It can be exploited over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-0125 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-2006-0125/ (Markdown: https://insights.sbomify.com/CVE-2006-0125/index.md)
```

## Sources

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

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