What is the severity of CVE-1999-0535?

CVE-1999-0535 has a high severity as it involves critical password policy settings that can lead to weak password practices.

How do I fix CVE-1999-0535?

To fix CVE-1999-0535, adjust the Windows NT account policy settings for password length, age, and uniqueness to enforce stronger security standards.

Who is affected by CVE-1999-0535?

CVE-1999-0535 affects users of Microsoft Windows NT and Microsoft Windows 2000 systems.

What can happen if I ignore CVE-1999-0535?

Ignoring CVE-1999-0535 can result in increased risk of unauthorized access due to weak password policies.

Is CVE-1999-0535 still relevant today?

While CVE-1999-0535 was identified in 1999, its implications may still be relevant for legacy systems using outdated password policies.

Vulnerability/
CVE-1999-0535

critical

CWE

NVD-CWE-Other

1/1/1997

4/2/2000

20/11/2024

CVE-1999-0535

First published: Wed Jan 01 1997(Updated: )

A Windows NT account policy for passwords has inappropriate, security-critical settings, e.g. for password length, password age, or uniqueness.

Credit: cve@mitre.org cve@mitre.org

Affected Software	Affected Version	How to fix
Microsoft Windows NT
Microsoft Windows 2000

Never miss a vulnerability like this again

Reference Links

https://exchange.xforce.ibmcloud.com/vulnerabilities/CVE-1999-0535

Frequently Asked Questions

What is the severity of CVE-1999-0535?
CVE-1999-0535 has a high severity as it involves critical password policy settings that can lead to weak password practices.
How do I fix CVE-1999-0535?
To fix CVE-1999-0535, adjust the Windows NT account policy settings for password length, age, and uniqueness to enforce stronger security standards.
Who is affected by CVE-1999-0535?
CVE-1999-0535 affects users of Microsoft Windows NT and Microsoft Windows 2000 systems.
What can happen if I ignore CVE-1999-0535?
Ignoring CVE-1999-0535 can result in increased risk of unauthorized access due to weak password policies.
Is CVE-1999-0535 still relevant today?
While CVE-1999-0535 was identified in 1999, its implications may still be relevant for legacy systems using outdated password policies.

collector/nvd-historical
vendor/microsoft
vendor/windows nt
vendor/windows 2000
collector/nvd-index
agent/type
agent/first-publish-date
collector/mitre-cve
source/MITRE
agent/severity
agent/weakness
agent/references
agent/description
collector/nvd-api
source/NVD
agent/software-canonical-lookup
agent/last-modified-date
agent/author
agent/softwarecombine
agent/event
agent/tags
agent/source
canonical/microsoft windows nt
canonical/microsoft windows 2000

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-1999-0535?
CVE-1999-0535 has a high severity as it involves critical password policy settings that can lead to weak password practices.
How do I fix CVE-1999-0535?
To fix CVE-1999-0535, adjust the Windows NT account policy settings for password length, age, and uniqueness to enforce stronger security standards.
Who is affected by CVE-1999-0535?
CVE-1999-0535 affects users of Microsoft Windows NT and Microsoft Windows 2000 systems.
What can happen if I ignore CVE-1999-0535?
Ignoring CVE-1999-0535 can result in increased risk of unauthorized access due to weak password policies.
Is CVE-1999-0535 still relevant today?
While CVE-1999-0535 was identified in 1999, its implications may still be relevant for legacy systems using outdated password policies.