full-disclosure - RE: Full-Disclosure digest, Catching Sasser

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>] [day] [month] [year] [list]

From: shash at etisalat-nis.ae (Shashank Rai)
Subject: RE: Full-Disclosure digest, Catching Sasser

The number can vary from 1 to 32767. Furthermore, the way sasser ftp is implememented it really doesn't care what file name you provide as argument 
to the GET request. It just sends you a copy of the virus. Am sure the manual u r referring to read, mentions all this ;) 
The number in my script was an illustration. And may be the manual also mentioned that though you may get TCP SYN packets on port 445 you will not necessarily get the virus. Sasser first tries to determine the remote host OS type. If it windows 2000 or XP then only it attempts infection selecting the return address for the overflow. So starting a netcat listener on port 445 is not going to guaranty a copy of sasser.

But i'm sure THE MANUAL has it all ;)

cheers,
shashank

-----Original Message-----
From:	full-disclosure-admin@...ts.netsys.com on behalf of Thomas Springer
Sent:	Wed 05-May-04 16:12
To:	full-disclosure@...ts.netsys.com
Cc:	
Subject:	Re: [Full-Disclosure] RE: Full-Disclosure digest, Catching Sasser
RTFM - the 4digit-number mentioned is random. maybe it'll help to 
expand your script to try 9999 combinations or scan 10.000 infected 
hosts. It shouldn't be much of a problem to find them - we still 
experience >50 different sasser-ips per second hammering our firewall.