LiveActive security incident?Get immediate response
CVE Record

CVE-1999-0582: A Windows NT account policy has inappropriate, security-critical settings for lockout, e.g.

A Windows NT account policy has inappropriate, security-critical settings for lockout, e.g. lockout duration, lockout after bad logon attempts, etc.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This entry describes a Windows NT system whose account lockout policy is configured weakly, for example allowing too many bad password attempts or unlocking accounts too quickly. It is a configuration weakness rather than a software bug, making it easier for attackers to guess passwords through repeated login attempts.

Executive priority

Low priority for modern environments. Treat as a hardening checklist item during baseline reviews rather than an emergency. Elevate only if legacy Windows NT systems or unmanaged local accounts still exist within scope.

Technical view

CVE-1999-0582 catalogs a misconfiguration class in Windows NT account policies where lockout thresholds, lockout duration, or reset counters are set to permissive values. The public record provides no CVSS score, CWE mapping, or specific affected build. It reflects a hardening baseline concern rather than a discrete code vulnerability, aligned with the CVE program's early "configuration" entries.

Likely exposure

Exposure is limited to legacy Windows NT environments where account lockout policy remains permissive. Modern Windows Server and Active Directory deployments typically define stricter defaults, so exposure in current enterprises is minimal outside of unmanaged legacy hosts or forgotten local accounts.

Exploitation context

Not listed in CISA KEV. The source bundle does not cite active exploitation. Weak lockout settings historically enable online password guessing and brute-force attempts against interactive or network logons, but no specific exploit campaign is referenced in the provided sources.

Researcher notes

This is a legacy CVE-numbered configuration issue with no CVSS, CWE, KEV listing, or affected-product enumeration in the source bundle. Treat it as a policy-hygiene reference. For current work, map lockout hardening to modern controls (NIST 800-53 AC-7, CIS Windows Benchmarks) and validate against present-day Microsoft baselines rather than the 1999 text.

Mitigation direction

  • Set account lockout threshold, duration, and reset window per current CIS or Microsoft security baselines.
  • Enforce strong password policy and, where possible, multi-factor authentication on interactive logons.
  • Retire or isolate remaining Windows NT hosts, as they are unsupported by Microsoft.
  • Consult current Microsoft security guidance rather than the 1999 record for authoritative hardening values.

Validation and detection

  • Review Group Policy and local security policy for lockout threshold, duration, and reset counter values.
  • Audit domain and local accounts for lockout policy inheritance using tools such as secpol.msc or gpresult.
  • Correlate authentication failure events (e.g., 4625/529) to detect brute-force attempts against weakly protected accounts.
  • Confirm no in-scope hosts still run Windows NT; if any remain, document compensating controls.
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-0582 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.