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

> Local attackers can read arbitrary files via symlink attacks on the rlmadmin utility in Merit AAA Server.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Feb 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-26f7-xg4p-fj4g

## What is CVE-2001-1000?

CVE-2001-1000 is a low-severity path traversal vulnerability in n/a, published on 2 Feb 2002. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

rlmadmin RADIUS management utility in Merit AAA Server 3.8M, 5.01, and possibly other versions, allows local users to read arbitrary files via a symlink attack on the rlmadmin.help file.

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

It affects 1 product.


Products: Merit Aaa Radius Server.

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

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

## Is CVE-2001-1000 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2001-1000 exists.

Public exploit code:

- Merit AAA RADIUS Server 3.8 - rlmadmin Symbolic Link (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2001-1000 is a low-severity path traversal vulnerability in n/a, published on 2 Feb 2002. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2001-1000 exists.

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-1000/ (Markdown: https://insights.sbomify.com/CVE-2001-1000/index.md)
```

## Sources

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

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