Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-1999-1363: Windows NT 3.51 and 4.0 allow local users to cause a denial of service (crash) by running a program

0
Low
VulnerabilityCVE-1999-1363cve-1999-1363denial of service
Published: Fri Dec 31 1999 (12/31/1999, 05:00:00 UTC)
Source: NVD
Vendor/Project: microsoft
Product: windows_nt

Description

Windows NT 3.51 and 4.0 allow local users to cause a denial of service (crash) by running a program that creates a large number of locks on a file, which exhausts the NonPagedPool.

AI-Powered Analysis

AILast updated: 07/01/2025, 11:12:43 UTC

Technical Analysis

CVE-1999-1363 is a vulnerability affecting Microsoft Windows NT versions 3.51 and 4.0. The issue allows a local user to cause a denial of service (DoS) condition by executing a program that creates an excessive number of locks on a file. This behavior exhausts the system's NonPagedPool memory, a critical kernel memory pool used for objects that cannot be paged out to disk. When this memory is depleted, the operating system becomes unstable and may crash, resulting in a denial of service. The vulnerability requires local access to the system, meaning an attacker must already have some level of access to the machine to exploit it. The CVSS score assigned is 2.1 (low severity), reflecting that the impact is limited to availability, with no impact on confidentiality or integrity, and that exploitation does not require elevated privileges but does require local access. There are no known patches or fixes available for this vulnerability, and no known exploits have been observed in the wild. Given the age of the affected operating systems (Windows NT 3.51 and 4.0 were released in the mid-1990s), these systems are largely obsolete and rarely used in modern environments.

Potential Impact

For European organizations, the direct impact of this vulnerability today is minimal due to the obsolescence of Windows NT 3.51 and 4.0 in production environments. However, if legacy systems running these versions are still in use—such as in industrial control systems, embedded devices, or specialized legacy applications—this vulnerability could be exploited by an insider or a local attacker to cause system crashes and disrupt operations. The denial of service could lead to downtime, loss of availability of critical services, and potential operational delays. Since the vulnerability does not affect confidentiality or integrity, the risk is limited to availability. Organizations relying on legacy Windows NT systems should be aware of this risk, especially in sectors where legacy systems are more prevalent, such as manufacturing or utilities. Overall, the impact is low for most modern European enterprises but could be higher in niche legacy-dependent environments.

Mitigation Recommendations

Given that no patches are available for this vulnerability, mitigation focuses on minimizing the risk of exploitation. Organizations should: 1) Identify and inventory any legacy systems running Windows NT 3.51 or 4.0 and assess their criticality. 2) Restrict local access to these systems to trusted personnel only, implementing strict access controls and monitoring. 3) Where possible, isolate legacy systems from broader networks to reduce the risk of unauthorized local access. 4) Consider upgrading or migrating legacy systems to supported operating systems to eliminate the vulnerability entirely. 5) Implement host-based monitoring to detect unusual file locking behavior that could indicate an attempted exploit. 6) Educate users with local access about the risks of running untrusted programs on legacy systems. These steps help reduce the likelihood of exploitation and limit potential operational disruptions.

Need more detailed analysis?Upgrade to Pro Console

Threat ID: 682ca32db6fd31d6ed7df669

Added to database: 5/20/2025, 3:43:41 PM

Last enriched: 7/1/2025, 11:12:43 AM

Last updated: 2/3/2026, 6:51:47 AM

Views: 54

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats