Quick answers
- Is CVE-1999-0535 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-1999-0535 being exploited in the wild.
- How severe is CVE-1999-0535?
- Critical severity, with a CVSS score of 10, published 1 January 1997.
- Which products and versions are affected?
- Microsoft Windows NT.
- Is there a fix for CVE-1999-0535?
- 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-0535 attacked?
- It is attacked over the network, in an operating system.
- Am I affected by CVE-1999-0535?
- 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 entry describes a configuration-based vulnerability where Windows NT account policies are set to insecure values. Specifically, the policy may lack adequate enforcement for minimum password length, maximum password age, or password history (uniqueness). An attacker can leverage these weak requirements to perform brute-force or credential-guessing attacks more effectively. Because this is a policy configuration issue rather than a code flaw, the primary remediation is for administrators to manually harden the account policy settings within the operating system. Successful exploitation can lead to complete system compromise (Full Confidentiality, Integrity, and Availability impact).
Affected products
- Microsoft Windows NT
Timeline
- 1997-01-01: disclosed