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

> Local attackers can create or overwrite arbitrary files in Sun Ray Server Software via the utxconfig utility.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Aug 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-gmvc-5g7r-xxcq

## What is CVE-2006-4049?

CVE-2006-4049 is a low-severity path traversal vulnerability in n/a, published on 9 Aug 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unspecified vulnerability in the utxconfig utility in Sun Ray Server Software 3.x allows local users to create or overwrite arbitrary files via unknown attack vectors.

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

It affects 1 product.


Products: Sun Ray Server Software.

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

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

## Is CVE-2006-4049 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-4294](https://insights.sbomify.com/CVE-2009-4294/): Other in n/a (critical 10.0)
- [CVE-2008-2112](https://insights.sbomify.com/CVE-2008-2112/): Privilege escalation in n/a (high 8.5)
- [CVE-2009-4295](https://insights.sbomify.com/CVE-2009-4295/): Weak cryptography in n/a (high 7.8)
- [CVE-2007-6482](https://insights.sbomify.com/CVE-2007-6482/): Denial of service in n/a (high 7.8)
- [CVE-2008-5422](https://insights.sbomify.com/CVE-2008-5422/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-4049 is a low-severity path traversal vulnerability in n/a, published on 9 Aug 2006. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-4049 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-4049/ (Markdown: https://insights.sbomify.com/CVE-2006-4049/index.md)
```

## Sources

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

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