Security readout for executives and security teams
A logged-in local user on Windows 2000 could block new Group Policy settings from applying by locking policy files. That can stop security configuration changes from reaching a machine, undermining central control. The issue matters mainly where Windows 2000 remains in service or archival environments. Exposure is likely limited to legacy Windows 2000 systems that process Group Policy. The provided affected-product fields are incomplete, so confirm actual exposure through asset inventory rather than assuming all Windows environments are affected. Treat this as high priority only if Windows 2000 remains in the environment. For modern fleets, the main task is confirming absence. Any confirmed legacy exposure should be remediated or isolated because the flaw can undermine centralized security policy enforcement. Mitigation focus: Identify any remaining Windows 2000 systems in production, lab, or archival networks.; Check Microsoft MS02-016 and apply the vendor-recommended update or guidance where applicable.; Prioritize retirement, isolation, or compensating controls for unsupported Windows 2000 assets..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-667: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2002-0051 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- oval:org.mitre.oval:def:38CVE reference · vdb-entry, signature
- MS02-016CVE reference · vendor-advisory, x_refsource_MS
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Locking
Improper Locking represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.