Menu

Star on GitHub · 3.2k

CVE-1999-0701

7.2 · HIGH

After an unattended installation of Windows NT 4.0, an installation file could include sensitive information such as the local Administrator password.

Published Apr 11, 2000microsoftCWE-16EPSS 1.56%

Overview

CVE-1999-0701 is a high-severity vulnerability affecting microsoft windows_nt. It was published on April 11, 2000 and has a CVSS 2.0 base score of 7.2 (HIGH).

This vulnerability has a CVSS 2.0 base score of 7.2, rated HIGH. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical description

After an unattended installation of Windows NT 4.0, an installation file could include sensitive information such as the local Administrator password.

Remediation

Check the references section for vendor advisories and patches from microsoft. Update windows_nt to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-1999-0701?

CVE-1999-0701 is a high-severity vulnerability affecting microsoft windows_nt. It was published on April 11, 2000 and has a CVSS 2.0 base score of 7.2 (HIGH).

How severe is CVE-1999-0701?

This vulnerability has a CVSS 2.0 base score of 7.2, rated HIGH. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-1999-0701?

Check the references section for vendor advisories and patches from microsoft. Update windows_nt to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-1999-0701?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-1999-0701 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.