Malformed Request Causes LSA Service to Stop Responding

A specially malformed request to the Microsoft Local Security Authority (LSA) service may be used to exploit a security vulnerability on a computer running Windows NT. A user can abuse this vulnerability to run a program and cause a denial of service attack that may cause the LSA service to stop responding (hang) and require you to restart the computer. You may also receive the following error message:

Windows NT provides the ability to manage user privileges programmatically through the Local Security Authority (LSA) application programming interface (API). This API allows a program to query user names, modify privileges, and change other elements of the security policy, subject to the program's authorizations. Certain API methods do not correctly handle certain types of invalid arguments. If a call is made using a specially malformed argument, the LSA service may hang. The vulnerability is a denial of service threat only, and the LSA service can be restored by restarting the computer. This vulnerability cannot be used by unauthorized program to query or modify user information or privileges.

Windows NT Server or Workstation 4.0

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:

• http://www.microsoft.com/downloads/details.aspx?familyid=E396D059-E402-46EF-B095-A74399E25737&displaylang=en/ (http://www.microsoft.com/Windows/ServicePacks/) -or-
  
  
• 152734  (http://support.microsoft.com/kb/152734/EN-US/ ) how to obtain the latest windows nt 4.0 service pack

For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:
NOTE: This fix can be installed on Windows NT 4.0 Service Pack 4 and Service Pack 5.

Windows NT Server 4.0, Terminal Server Edition

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows NT Server version 4.0, Terminal Server Edition Service Pack 6.

For additional security-related information about Microsoft products, please visit: