Article ID: 222159
Article Last Modified on 11/1/2006
APPLIES TO
- Microsoft Windows NT Server 4.0 Standard Edition
- Microsoft Windows NT 4.0 Service Pack 1
- Microsoft Windows NT 4.0 Service Pack 2
- Microsoft Windows NT 4.0 Service Pack 3
- Microsoft Windows NT 4.0 Service Pack 4
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Server 4.0 Enterprise Edition
- Microsoft Windows NT 4.0 Service Pack 4
This article was previously published under Q222159
SYMPTOMS
When you modify the "\??" object folder's symbolic link table by substituting a different case (upper versus lower) letter in the table to point to a different device associated with a disk drive alias, it may be possible to bypass typical Windows NT security and allow any user to acquire administrator privileges.
RESOLUTION
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:
- 152734 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:
Once you have installed the Windows NT 4.0 service pack, it is necessary to enable base system object restrictions to prevent the use of this security exploit. To do this:
- Click Start, click Run, type regedt32, and then click OK.
- On the Windows menu, click HKEY_LOCAL_ MACHINE on Local Machine.
- Double-click the \System\CurrentControlSet\Control\Session Manager folder.
- Double-click the ProtectionMode value, type 1, and then click OK.
- Quit Registry Editor, and then restart the computer.
STATUS
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 4.0 Service Pack 5.
Keywords: kbbug kbfix kbqfe KB222159
