# CVE-1999-0902: Missing authorization in n/a

> Local administrators can modify password tables in ypserv due to missing authorization checks, allowing unauthorized data modification.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jan 2000
- **Updated:** 1 Aug 2024
- **Also known as:** AZL-37066, AZL-7456, GHSA-r774-h43h-88gg

## What is CVE-1999-0902?

CVE-1999-0902 is a high-severity missing authorization vulnerability in n/a, published on 4 Jan 2000. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

ypserv allows local administrators to modify password tables.

## Which versions are affected by CVE-1999-0902?

It affects 1 product.


Products: Linux-Nis Ypserv.

## How do I fix CVE-1999-0902?

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

## Is CVE-1999-0902 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-1999-0901](https://insights.sbomify.com/CVE-1999-0901/): Privilege escalation in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-1999-0902 and fix it if it is affected.

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

## Sources

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

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