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

> An attacker can read arbitrary files accessible by the Gopher daemon due to path traversal vulnerabilities in the server software.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jun 2000
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-6m79-q67f-8mqp

## What is CVE-1999-0124?

CVE-1999-0124 is a critical path traversal vulnerability in n/a, published on 2 Jun 2000. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerabilities in UMN gopher and gopher+ versions 1.12 and 2.0x allow an intruder to read any files that can be accessed by the gopher daemon.

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

It affects 1 product.


Products: University of Minnesota Gopherd.

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

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

## Is CVE-1999-0124 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2000-0743](https://insights.sbomify.com/CVE-2000-0743/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0560](https://insights.sbomify.com/CVE-2004-0560/): Integer overflow in n/a (high 7.5)
- [CVE-2004-0561](https://insights.sbomify.com/CVE-2004-0561/): Other in n/a (high 7.5)
- [CVE-2003-0805](https://insights.sbomify.com/CVE-2003-0805/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-1999-0124 is a critical path traversal vulnerability in n/a, published on 2 Jun 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-1999-0124 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-0124/ (Markdown: https://insights.sbomify.com/CVE-1999-0124/index.md)
```

## Sources

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

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