# CVE-1999-0741: Auth bypass in n/a

> Root users can log in without a password, allowing unauthorized privileged access to the system.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Feb 2000
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-hmmr-pvfg-gcfv

## What is CVE-1999-0741?

CVE-1999-0741 is a critical authentication bypass vulnerability in n/a, published on 4 Feb 2000. 

### Official description

QMS CrownNet Unix Utilities for 2060 allows root to log on without a password.

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

It affects 1 product.


Products: Qms Crownnet Unix Utilities.

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

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

## Is CVE-1999-0741 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-1999-0741 is a critical authentication bypass vulnerability in n/a, published on 4 Feb 2000. 
Exploitation: There is no known exploitation of CVE-1999-0741 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-0741/ (Markdown: https://insights.sbomify.com/CVE-1999-0741/index.md)
```

## Sources

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

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