2 replies
by dkolas
by a.jongsma
There are chances that someone already knows you're clients password, and that he uses a security hole of Windows 2000 to log into the box without leaving any logon/logoff traces in the Security log.
All versions of Windows NT do - under certain conditions - log successful logons, which normally create a Security event 528, as failed logon (Security event 539)!
Because the locking of the machine creates no Security event by design, a local attacker can use this hole to log onto a locked machine and lock this machine again (when he is done), without leaving logon/logoff traces of his successful break in in the Security log!
You could apply the fix KB article Q188700 (http://support.microsoft.com/default.aspx?scid=kb;EN-US;q188700) which will require you to add the following Registry value:
Key: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon
Value: ForceUnlockLogon
Type: DWORD
Content: 1 (on) or 0 (off)
Microsoft says it would be necessary toreboot. In all experiments we done, we always found that the change did immediately work, even without a reboot.
When ForceUnlockLogon is set to 1, a locked account can not unlock a locked machine. This means an attacker can not use the hole in the eventlog mechanism to logon undetected any longer.
This discussion is closed to new replies.
Trending Security posts
Sort by Trending