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

> Authenticated attackers can exploit a directory traversal flaw in JBoss AS to read, modify, or potentially execute arbitrary files on the server.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Nov 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-w88w-qrrp-j36h, RHSA-2006:0743

## What is CVE-2006-5750?

CVE-2006-5750 is a high-severity path traversal vulnerability in n/a, published on 27 Nov 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in the DeploymentFileRepository class in JBoss Application Server (jbossas) 3.2.4 through 4.0.5 allows remote authenticated users to read or modify arbitrary files, and possibly execute arbitrary code, via unspecified vectors related to the console manager.

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `jbossas` | Red Hat:rhel_application_stack:1 | All versions | 0:4.0.4-1.el4s1.25 |

Products: Jboss Jboss Application Server.

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

Apply the vendor's patch.

## Is CVE-2006-5750 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-1036](https://insights.sbomify.com/CVE-2007-1036/): Missing authorization in n/a (high 7.5)
- [CVE-2007-1354](https://insights.sbomify.com/CVE-2007-1354/): Race condition in n/a (medium 6.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-5750 is a high-severity path traversal vulnerability in n/a, published on 27 Nov 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-5750 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-5750/ (Markdown: https://insights.sbomify.com/CVE-2006-5750/index.md)
```

## Sources

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

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