# CVE-1999-0166: Path traversal in n/a

> An attacker can traverse directory boundaries to access or modify files outside the exported NFS share.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/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:** No
- **Published:** 29 Sep 1999
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-2jhf-gwmr-wr3c

## What is CVE-1999-0166?

CVE-1999-0166 is a medium-severity path traversal vulnerability in n/a, published on 29 Sep 1999. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

NFS allows users to use a "cd .." command to access other directories besides the exported file system.

## Which versions are affected by CVE-1999-0166?

It affects 1 product.


Products: Sun Nfs.

## How do I fix CVE-1999-0166?

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

## Is CVE-1999-0166 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-1999-0169](https://insights.sbomify.com/CVE-1999-0169/): Auth bypass in n/a (critical 10.0)
- [CVE-1999-0084](https://insights.sbomify.com/CVE-1999-0084/): Privilege escalation in n/a (high 8.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-1999-0166 and fix it if it is affected.

What it is: CVE-1999-0166 is a medium-severity path traversal vulnerability in n/a, published on 29 Sep 1999. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-1999-0166 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-1999-0166/ (Markdown: https://insights.sbomify.com/CVE-1999-0166/index.md)
```

## Sources

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

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