# CVE-1999-0603: Misconfiguration in n/a

> Misconfigured group memberships in Windows NT allow inappropriate users to gain elevated privileges, requiring administrative review of user groups.

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

## What is CVE-1999-0603?

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

### Official description

In Windows NT, an inappropriate user is a member of a group, e.g. Administrator, Backup Operators, Domain Admins, Domain Guests, Power Users, Print Operators, Replicators, System Operators, etc.

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


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

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

## Is CVE-1999-0603 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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