# CVE-2002-0444: Security feature bypass in n/a

> Authenticated users can bypass group policies on Windows Terminal Server when SYSVOL connection limits are reached, potentially violating security controls.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Sep 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-pjc3-7wx7-94c4

## What is CVE-2002-0444?

CVE-2002-0444 is a high-severity vulnerability in n/a, published on 1 Sep 2004. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Microsoft Windows 2000 running the Terminal Server 90-day trial version, and possibly other versions, does not apply group policies to incoming users when the number of connections to the SYSVOL share exceeds the maximum, e.g. with a maximum number of licenses, which can allow remote authenticated users to bypass group policies.

## Which versions are affected by CVE-2002-0444?

It affects 1 product.


Products: Microsoft Windows 2000 Terminal Services.

## How do I fix CVE-2002-0444?

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

## Is CVE-2002-0444 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-1933](https://insights.sbomify.com/CVE-2002-1933/): Security feature bypass in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-0444 and fix it if it is affected.

What it is: CVE-2002-0444 is a high-severity vulnerability in n/a, published on 1 Sep 2004. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-0444 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-2002-0444/ (Markdown: https://insights.sbomify.com/CVE-2002-0444/index.md)
```

## Sources

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

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