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

> Local users can print arbitrary files due to missing permission checks in the LPPlus dccscan setuid program.

- **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:** 18 Oct 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-mhr6-m9pw-wprq

## What is CVE-2000-0881?

CVE-2000-0881 is a low-severity missing authorization vulnerability in n/a, published on 18 Oct 2000. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The dccscan setuid program in LPPlus does not properly check if the user has the permissions to print the file that is specified to dccscan, which allows local users to print arbitrary files.

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

It affects 1 product.


Products: Plus Technologies Lpplus.

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

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

## Is CVE-2000-0881 being exploited?

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

Public exploit code:

- LPPlus 3.2.2/3.3 - dccscan Unprivileged read (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2000-0880](https://insights.sbomify.com/CVE-2000-0880/): Privilege escalation in n/a (low 3.6)
- [CVE-2000-0879](https://insights.sbomify.com/CVE-2000-0879/): Privilege escalation in n/a (low 2.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2000-0881 is a low-severity missing authorization vulnerability in n/a, published on 18 Oct 2000. 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-2000-0881 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-2000-0881/ (Markdown: https://insights.sbomify.com/CVE-2000-0881/index.md)
```

## Sources

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

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