bugtraq - Sasser variant that effects 2k3 SP1 completely updated?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <000701c646d1$353bf9b0$6200bed1@thenap.com>
Date: Mon, 13 Mar 2006 14:06:13 -0500
From: "Andrew Weaver" <aweaver@...net>
To: <bugtraq@...urityfocus.com>
Subject: Sasser variant that effects 2k3 SP1 completely updated?

    Has anyone seen a sasser variant that effects Windows 2k3 SP1?

    We have started seeing servers exhibiting the exact same effects that 
sasser had back when it was "all the rage" that are completely patched to 
the latest "Windows Update" spec before ever touching the non firewalled 
internet. Our firewall is about as restrictive as possible.

There are two errors which are similar which evoke the "reboot of death" I 
have been seeing these again since Saturday.

"Shutdown was initiated by NT AUTHORITY\SYSTEM
C:\Windows\SYSTEM32\services.exe Status Code -1073741819"

I shortened the above error message, but the perinent parts are there, I 
also noticed that sometimes it is lsass and sometimes it is services.exe.

Also, we use ghost to install our operating system, and our ghost image is 
current up to the last windows update patch, and I have verified that sasser 
is not on our ghost image.

Has anyone seen anything similar?

Thanks,
Andrew