LiveActive security incident?Get immediate response
CVE Record

CVE-1999-0580: The HKEY_LOCAL_MACHINE key in a Windows NT system has inappropriate, system-critical permissions.

The HKEY_LOCAL_MACHINE key in a Windows NT system has inappropriate, system-critical permissions.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This decades-old finding describes a Windows NT system where the HKEY_LOCAL_MACHINE registry key was left with permissions that were too permissive for such a system-critical resource. In practical terms, a user or process with limited access could reach or modify settings that should be reserved for administrators, weakening the trust boundary of the operating system on affected legacy hosts.

Executive priority

Low priority for modern environments. Treat as a legacy hygiene item: if any Windows NT systems remain, prioritize their retirement or isolation as part of standard technical-debt reduction rather than as an incident-grade response.

Technical view

CVE-1999-0580 records a configuration weakness in Windows NT where the HKEY_LOCAL_MACHINE registry hive carries inappropriate access control lists on system-critical keys. Overly broad permissions on HKLM can allow non-privileged principals to read sensitive values or alter service, driver, and security-relevant configuration, which is a classic path to privilege escalation or persistence. No CVSS score, CWE mapping, or patch reference is included in the provided bundle.

Likely exposure

Exposure is limited to legacy Windows NT systems that remain in production or lab use. Modern Windows releases ship with tightened default registry ACLs, so mainstream fleets are unlikely to be affected. Risk concentrates in unsupported industrial, embedded, or air-gapped environments where NT-era hosts still run business or operational technology workloads.

Exploitation context

The provided sources do not indicate active exploitation, and this CVE is not listed in CISA KEV per the bundle. It is a hardening/misconfiguration advisory from 1999 rather than a discrete exploitable vulnerability with public tooling. Any abuse would require an authenticated local foothold on an affected NT host to leverage the loose registry permissions.

Researcher notes

The record is a sparse 1999-era entry with no CVSS, CWE, affected product list, or vendor advisory in the bundle. Treat it as a configuration-hardening reference, not a modern vulnerability with a patch. Validate by direct ACL inspection on any surviving NT hosts, and rely on current Microsoft security baselines for supported operating systems rather than extrapolating from this entry.

Mitigation direction

  • Inventory any remaining Windows NT hosts and plan migration off unsupported platforms.
  • Apply Microsoft's historical NT hardening guidance to tighten HKLM registry ACLs.
  • Restrict interactive and network logon to trusted administrators on legacy hosts.
  • Isolate legacy NT systems on segmented networks with strict egress controls.
  • Consult current Microsoft documentation for supported OS registry hardening baselines.

Validation and detection

  • Enumerate HKLM subkey permissions and compare against a hardened NT baseline.
  • Confirm non-administrative principals lack write access to sensitive HKLM subtrees.
  • Review audit logs for unexpected registry modifications on legacy hosts.
  • Verify legacy NT assets are accounted for in the CMDB and network segmentation policy.
  • Re-scan configurations after applying hardening to confirm ACL changes persist.
Prepared
Confidence
medium
Sources
2

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

cve · low confidence lookup

CVE-1999-0580 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.