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-0227: Access violation in LSASS.EXE (LSA/LSARPC) program in Windows NT allows a denial of service.

0
Medium
VulnerabilityCVE-1999-0227cve-1999-0227denial of servicecwe-264
Published: Sun Jun 01 1997 (06/01/1997, 04:00:00 UTC)
Source: NVD
Vendor/Project: microsoft
Product: windows_nt

Description

Access violation in LSASS.EXE (LSA/LSARPC) program in Windows NT allows a denial of service.

AI-Powered Analysis

AILast updated: 07/01/2025, 23:55:44 UTC

Technical Analysis

CVE-1999-0227 is a vulnerability identified in the LSASS.EXE process, specifically within the LSA/LSARPC component of Microsoft Windows NT version 4.0. LSASS.EXE (Local Security Authority Subsystem Service) is a critical system process responsible for enforcing security policies, handling authentication, and managing Active Directory services. The vulnerability manifests as an access violation error, which can be triggered remotely without authentication (as indicated by the CVSS vector AV:N/AC:L/Au:N). This access violation leads to a denial of service (DoS) condition, causing the LSASS process to crash. Since LSASS is integral to system security and stability, its failure typically results in a system reboot or a forced logoff, disrupting normal operations. The vulnerability does not impact confidentiality or integrity but affects availability. No patches are available for this vulnerability, and there are no known exploits in the wild. Given the age of the affected product (Windows NT 4.0) and the lack of patch availability, this vulnerability primarily concerns legacy systems that may still be in operation in some environments. The CWE-264 classification indicates improper access control, which in this case allows unauthenticated remote attackers to cause a denial of service by exploiting the access violation in LSASS.EXE.

Potential Impact

For European organizations, the impact of this vulnerability is largely dependent on whether legacy Windows NT 4.0 systems are still in use. In modern environments, this vulnerability is unlikely to pose a direct threat due to the obsolescence of the affected OS version. However, organizations that maintain legacy infrastructure for critical applications or industrial control systems may face service disruptions if this vulnerability is exploited. The denial of service could interrupt authentication services, leading to downtime in network access, application availability, and potentially impacting business continuity. This could be particularly problematic for sectors with strict uptime requirements such as finance, healthcare, and government institutions. Additionally, the forced reboot or logoff caused by LSASS failure could result in data loss or corruption if unsaved work is interrupted. While no known exploits exist, the ease of triggering the DoS remotely without authentication means that if attackers target legacy systems, they could cause operational disruptions with minimal effort.

Mitigation Recommendations

Given that no patch is available for this vulnerability, European organizations should prioritize the following mitigation strategies: 1) Decommission or upgrade legacy Windows NT 4.0 systems to supported versions of Windows that receive security updates. 2) Isolate legacy systems from external networks using network segmentation and firewalls to limit exposure to unauthenticated remote attacks. 3) Implement strict access controls and monitor network traffic for unusual activity targeting LSASS or related services. 4) Employ intrusion detection and prevention systems (IDS/IPS) configured to detect anomalous RPC calls or access violations related to LSASS. 5) Regularly back up critical data and ensure disaster recovery plans are in place to minimize impact from potential DoS events. 6) Conduct security audits to identify any remaining legacy systems and assess their risk posture. These steps go beyond generic advice by focusing on legacy system management, network isolation, and proactive monitoring tailored to the nature of this vulnerability.

Need more detailed analysis?Upgrade to Pro Console

Threat ID: 682ca32ab6fd31d6ed7de6eb

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

Last enriched: 7/1/2025, 11:55:44 PM

Last updated: 2/7/2026, 8:59:05 AM

Views: 36

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