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

> Attackers can overwrite arbitrary files and change ownership in Heimdal rshd when credential forwarding is enabled, potentially leading to privilege escalation.

- **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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-0582, GHSA-j7vw-pxhm-2jvf

## What is CVE-2006-0582?

CVE-2006-0582 is a low-severity path traversal vulnerability in n/a, published on 8 Feb 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unspecified vulnerability in rshd in Heimdal 0.6.x before 0.6.6 and 0.7.x before 0.7.2, when storing forwarded credentials, allows attackers to overwrite arbitrary files and change file ownership via unknown vectors.

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

It affects 1 product.


Products: Kth Heimdal.

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

Upgrade to a fixed version.

## Is CVE-2006-0582 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-1225](https://insights.sbomify.com/CVE-2002-1225/): Memory corruption in n/a (critical 10.0)
- [CVE-2002-1226](https://insights.sbomify.com/CVE-2002-1226/): Privilege escalation in n/a (critical 10.0)
- [CVE-2006-0677](https://insights.sbomify.com/CVE-2006-0677/): Null dereference in n/a (high 7.8)
- [CVE-2004-0371](https://insights.sbomify.com/CVE-2004-0371/): Auth bypass in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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