# CVE-1999-0582: Microsoft Windows NT insecure account lockout policy configuration

Source: https://junglewise.ai/threats/cve-1999-0582-microsoft-windows-nt-insecure-account-lockout-policy-configuration  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 1997-01-01. Updated: 2026-05-10  
License: CC BY 4.0 with a link back

CVE-1999-0582 · Severity: medium · CVSS 5 · Published 1997-01-01

Microsoft Windows NT systems may be configured with weak account lockout policies. This allows an attacker to repeatedly guess user passwords without the account being automatically disabled or locked. If exploited, this could lead to unauthorized access to corporate data or system resources through successful brute-force attacks.

Technologies: [Microsoft Windows 2000](https://junglewise.ai/threats/technologies/windows-2000), [Microsoft Windows Nt](https://junglewise.ai/threats/technologies/windows-nt). Vendors: [Microsoft](https://junglewise.ai/threats/vendors/microsoft).

## Quick answers

**Is CVE-1999-0582 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-1999-0582 being exploited in the wild.

**How severe is CVE-1999-0582?** Medium severity, with a CVSS score of 5, published 1 January 1997.

**Which products and versions are affected?** Microsoft Windows NT.

**Is there a fix for CVE-1999-0582?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-1999-0582 attacked?** It is attacked over the network, in an operating system.

**Am I affected by CVE-1999-0582?** Check whether you run Microsoft Windows 2000 or Microsoft Windows Nt. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

This vulnerability stems from insecure default or manual configurations of the Windows NT account lockout policy. Specifically, it involves settings where the 'lockout threshold' (number of failed attempts) is too high or disabled, and the 'lockout duration' is too short. An unauthenticated attacker with network access to the authentication interface can perform automated brute-force or dictionary attacks against user accounts. Because the policy does not sufficiently throttle or block these attempts, the probability of a successful credential compromise is significantly increased. Administrators should review and harden account lockout policies to ensure accounts are disabled after a reasonable number of failed attempts.

## Affected products

- Microsoft Windows NT

## Timeline

- 1997-01-01: disclosed

## References

- [https://www.cve.org/CVERecord?id=CVE-1999-0582](https://www.cve.org/CVERecord?id=CVE-1999-0582)

## Related threats

- [Microsoft Windows NT OS Kernel privilege escalation via integer underflow](https://junglewise.ai/threats/cve-2026-42980-microsoft-windows-nt-os-kernel-privilege-escalation-via-integer)
- [Microsoft Windows NT OS Kernel privilege escalation via integer underflow](https://junglewise.ai/threats/cve-2026-42916-microsoft-windows-nt-os-kernel-privilege-escalation-via-integer)
- [Microsoft DirectX NULL byte overwrite in QuickTime Movie Parser Filter](https://junglewise.ai/threats/cve-2009-1537-microsoft-directx-null-byte-overwrite-in-quicktime-movie-parser)
- [Microsoft Windows NT denial of service in SMB logon request](https://junglewise.ai/threats/cve-1999-0225-microsoft-windows-nt-denial-of-service-in-smb-logon-request)
- [Microsoft Windows TCP/IP stack denial of service in IP fragmentation](https://junglewise.ai/threats/cve-1999-0258-microsoft-windows-tcp-ip-stack-denial-of-service-in-ip)