CVE-1999-1360: Windows NT 4.0 allows local users to cause a denial of service via a user mode application that clos
Windows NT 4.0 allows local users to cause a denial of service via a user mode application that closes a handle that was opened in kernel mode, which causes a crash when the kernel attempts to close the handle.
AI Analysis
Technical Summary
CVE-1999-1360 is a vulnerability affecting Microsoft Windows NT 4.0, an operating system released in the mid-1990s. The issue arises when a local user executes a user-mode application that improperly closes a handle originally opened in kernel mode. Handles are references used by the operating system to manage resources such as files, devices, or synchronization objects. In this case, closing a kernel-mode handle from user mode leads to a situation where the kernel attempts to close the handle again, resulting in a system crash or denial of service (DoS). This vulnerability does not allow for privilege escalation or data compromise but can cause system instability and unavailability. The CVSS score of 2.1 reflects a low severity, primarily because exploitation requires local access, has low complexity, no authentication, and impacts only availability without affecting confidentiality or integrity. No patches are available for this vulnerability, and there are no known exploits in the wild. Given the age of Windows NT 4.0 and its obsolescence, this vulnerability is largely of historical interest, but it highlights risks in legacy systems that may still be in use in some environments.
Potential Impact
For European organizations, the impact of CVE-1999-1360 is generally minimal due to the obsolescence of Windows NT 4.0. However, any legacy systems still running this OS could be vulnerable to local denial of service attacks, potentially causing system crashes and operational disruptions. This could affect critical infrastructure or industrial control systems if such legacy systems are still in use, leading to downtime and productivity loss. Since the vulnerability requires local user access, the risk is limited to insiders or attackers who have already gained some level of access. The lack of confidentiality or integrity impact reduces the risk of data breaches, but availability interruptions could still have operational consequences, especially in environments where continuous uptime is critical.
Mitigation Recommendations
Given that no official patch exists for this vulnerability, European organizations should prioritize the following mitigations: 1) Upgrade or replace legacy Windows NT 4.0 systems with supported, modern operating systems to eliminate exposure. 2) Restrict local user access on legacy systems to trusted personnel only, minimizing the risk of exploitation. 3) Employ strict access controls and monitoring to detect and prevent unauthorized local access attempts. 4) Use virtualization or sandboxing to isolate legacy applications if upgrading is not immediately feasible. 5) Implement robust incident response procedures to quickly recover from any denial of service incidents. 6) Regularly audit and inventory legacy systems to identify and plan for their decommissioning or upgrade.
Affected Countries
Germany, France, United Kingdom, Italy, Spain, Poland, Netherlands
CVE-1999-1360: Windows NT 4.0 allows local users to cause a denial of service via a user mode application that clos
Description
Windows NT 4.0 allows local users to cause a denial of service via a user mode application that closes a handle that was opened in kernel mode, which causes a crash when the kernel attempts to close the handle.
AI-Powered Analysis
Technical Analysis
CVE-1999-1360 is a vulnerability affecting Microsoft Windows NT 4.0, an operating system released in the mid-1990s. The issue arises when a local user executes a user-mode application that improperly closes a handle originally opened in kernel mode. Handles are references used by the operating system to manage resources such as files, devices, or synchronization objects. In this case, closing a kernel-mode handle from user mode leads to a situation where the kernel attempts to close the handle again, resulting in a system crash or denial of service (DoS). This vulnerability does not allow for privilege escalation or data compromise but can cause system instability and unavailability. The CVSS score of 2.1 reflects a low severity, primarily because exploitation requires local access, has low complexity, no authentication, and impacts only availability without affecting confidentiality or integrity. No patches are available for this vulnerability, and there are no known exploits in the wild. Given the age of Windows NT 4.0 and its obsolescence, this vulnerability is largely of historical interest, but it highlights risks in legacy systems that may still be in use in some environments.
Potential Impact
For European organizations, the impact of CVE-1999-1360 is generally minimal due to the obsolescence of Windows NT 4.0. However, any legacy systems still running this OS could be vulnerable to local denial of service attacks, potentially causing system crashes and operational disruptions. This could affect critical infrastructure or industrial control systems if such legacy systems are still in use, leading to downtime and productivity loss. Since the vulnerability requires local user access, the risk is limited to insiders or attackers who have already gained some level of access. The lack of confidentiality or integrity impact reduces the risk of data breaches, but availability interruptions could still have operational consequences, especially in environments where continuous uptime is critical.
Mitigation Recommendations
Given that no official patch exists for this vulnerability, European organizations should prioritize the following mitigations: 1) Upgrade or replace legacy Windows NT 4.0 systems with supported, modern operating systems to eliminate exposure. 2) Restrict local user access on legacy systems to trusted personnel only, minimizing the risk of exploitation. 3) Employ strict access controls and monitoring to detect and prevent unauthorized local access attempts. 4) Use virtualization or sandboxing to isolate legacy applications if upgrading is not immediately feasible. 5) Implement robust incident response procedures to quickly recover from any denial of service incidents. 6) Regularly audit and inventory legacy systems to identify and plan for their decommissioning or upgrade.
Affected Countries
Threat ID: 682ca32db6fd31d6ed7df665
Added to database: 5/20/2025, 3:43:41 PM
Last enriched: 7/1/2025, 11:13:13 AM
Last updated: 2/7/2026, 10:09:08 AM
Views: 37
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-25764: CWE-80: Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) in opf openproject
LowCVE-2026-25592: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in microsoft semantic-kernel
CriticalCVE-2026-25729: CWE-863: Incorrect Authorization in lintsinghua DeepAudit
LowCVE-2025-15320: Multiple Binds to the Same Port in Tanium Tanium Client
LowCVE-2026-25724: CWE-61: UNIX Symbolic Link (Symlink) Following in anthropics claude-code
LowActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
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.