# CVE-2002-2000: Missing authorization in n/a

> Attackers can access unauthorized data in ACMS on OpenVMS due to improper use of process privileges.

- **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:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jul 2005
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-g3p4-jpvc-gvq8

## What is CVE-2002-2000?

CVE-2002-2000 is a low-severity missing authorization vulnerability in n/a, published on 14 Jul 2005. 

### Official description

ACMS 4.3 and 4.4 in OpenVMS Alpha 7.2 and 7.3 does not properly use process privileges, which allows attackers to access data.

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

It affects 1 product.


Products: Compaq Acms.

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

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

## Is CVE-2002-2000 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2002-2000 is a low-severity missing authorization vulnerability in n/a, published on 14 Jul 2005. 
Exploitation: There is no known exploitation of CVE-2002-2000 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-2002-2000/ (Markdown: https://insights.sbomify.com/CVE-2002-2000/index.md)
```

## Sources

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

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