# CVE-2001-0845: Missing authorization in n/a

> Local users can gain unauthorized access to resources in DECwindows Motif Server on OpenVMS systems.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 22 Nov 2001
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-83pj-9hmm-7pxf

## What is CVE-2001-0845?

CVE-2001-0845 is a medium-severity missing authorization vulnerability in n/a, published on 22 Nov 2001. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Vulnerability in DECwindows Motif Server on OpenVMS VAX or Alpha 6.2 through 7.3, and SEVMS VAX or Alpha 6.2, allows local users to gain access to unauthorized resources.

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

It affects 4 products.


Products: Dec Dec Openvms, Dec Dec Openvms Alpha, Dec Sevms, Dec Sevms Alpha.

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

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

## Is CVE-2001-0845 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-1999-1395](https://insights.sbomify.com/CVE-1999-1395/): Privilege escalation in n/a (high 7.2)
- [CVE-1999-1315](https://insights.sbomify.com/CVE-1999-1315/): Vulnerabilities in DECnet/OSI for OpenVMS before 5.8 on DEC Alpha AXP and VAX/VMS systems allow local users to gain privileges or cause a denial of service. (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2001-0845 is a medium-severity missing authorization vulnerability in n/a, published on 22 Nov 2001. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2001-0845 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-0845/ (Markdown: https://insights.sbomify.com/CVE-2001-0845/index.md)
```

## Sources

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

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