# CVE-2001-0068: Path traversal in n/a

> Remote attackers can read files outside the applet context via malicious applets in Mac OS Runtime for Java, requiring user interaction to load the applet.

- **Severity:** Low 2.6 (`AV:N/AC:H/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Feb 2001
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-g2qx-p2rm-qq6g

## What is CVE-2001-0068?

CVE-2001-0068 is a low-severity path traversal vulnerability in n/a, published on 2 Feb 2001. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Mac OS Runtime for Java (MRJ) 2.2.3 allows remote attackers to use malicious applets to read files outside of the CODEBASE context via the ARCHIVE applet parameter.

## Which versions are affected by CVE-2001-0068?

It affects 1 product.


Products: Apple Mac Os Runtime for Java.

## How do I fix CVE-2001-0068?

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

## Is CVE-2001-0068 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2000-0563](https://insights.sbomify.com/CVE-2000-0563/): Server-side request forgery in n/a (critical 10.0)
- [CVE-2001-1480](https://insights.sbomify.com/CVE-2001-1480/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-0068 and fix it if it is affected.

What it is: CVE-2001-0068 is a low-severity path traversal vulnerability in n/a, published on 2 Feb 2001. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2001-0068 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-2001-0068/ (Markdown: https://insights.sbomify.com/CVE-2001-0068/index.md)
```

## Sources

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

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