# CVE-2000-0845: Path traversal in n/a

> Remote attackers can read arbitrary files on Digital Unix systems by exploiting a path traversal vulnerability in the kdebug daemon.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Oct 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-2pvg-4x8f-qx36

## What is CVE-2000-0845?

CVE-2000-0845 is a medium-severity path traversal vulnerability in n/a, published on 18 Oct 2000. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

kdebug daemon (kdebugd) in Digital Unix 4.0F allows remote attackers to read arbitrary files by specifying the full file name in the initialization packet.

## Which versions are affected by CVE-2000-0845?

It affects 1 product.


Products: Digital Unix.

## How do I fix CVE-2000-0845?

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

## Is CVE-2000-0845 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-1999-1210](https://insights.sbomify.com/CVE-1999-1210/): Path traversal in n/a (high 7.2)
- [CVE-1999-1458](https://insights.sbomify.com/CVE-1999-1458/): Memory corruption in n/a (high 7.2)
- [CVE-2001-0369](https://insights.sbomify.com/CVE-2001-0369/): Memory corruption in n/a (high 7.2)
- [CVE-1999-0358](https://insights.sbomify.com/CVE-1999-0358/): Memory corruption in n/a (high 7.2)
- [CVE-1999-0406](https://insights.sbomify.com/CVE-1999-0406/): Memory corruption in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2000-0845 and fix it if it is affected.

What it is: CVE-2000-0845 is a medium-severity path traversal vulnerability in n/a, published on 18 Oct 2000. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2000-0845 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-2000-0845/ (Markdown: https://insights.sbomify.com/CVE-2000-0845/index.md)
```

## Sources

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

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