full-disclosure - MSBLASTER - aka LOVESAN/POZA ?

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

Message-ID: <200308130831.h7D8VTKR016475@caligula.anu.edu.au>
From: avalon at caligula.anu.edu.au (Darren Reed)
Subject: MSBLASTER - aka LOVESAN/POZA ?

In some mail from cstone, sie said:
> 
> On Wed, Aug 13, 2003 at 10:10:20AM +1000, Darren Reed wrote:
> > 
> > I've seen some people referring to MSBLASTER as "LOVESAN" and "POZA" as
> > all being the same thing.
> > 
> > Does this make sense to anyone else ?
> 
> yes.  everyone picks their own name -- this happens pretty
> frequently with malware.
> 
> from symantec's description of "W32.Blaster.Worm" (their name for
> it), available at:
> http://www.symantec.com/avcenter/venc/data/w32.blaster.worm.html
> 
> Also Known As: W32/Lovsan.worm [McAfee], Win32.Poza [CA], Lovsan
> [F-Secure], WORM_MSBLAST.A [Trend], W32/Blaster-A [Sophos],
> W32/Blaster [Panda]

Cripes.  Someone needs to have a central authority on naming for
these things, like the CVP#'s that are available or just dispense
with names and use a centrally allocated number.  Then I suppose
how do you have "extra" viruses that one company knows about but
another doesn't.

Enough of a mess to make you want to vomit massively all over their
doorstops.  And people wonder why computer security is a mess - not
even the necessary "responsible" vendors have enough sense to have
something resembling co-ordination & co-operation.

Darren