Sasser virus

I read alot about this Vasser worm or virus and that
Microsoft has a patch for it. I run Windows update and
there are no updates available for my system. Windows ME.
I then check my install history for updates and the patch
for this Sasser MS835732 does not show as being installed.

I have Works Suite 2000.

Should I manually install this patch or just forget about
it. I don't appear to be infected.

Thanks

zz
Wed May 05 11:10:36 CDT 2004

Ron wrote:

> I read alot about this Vasser worm or virus and that
> Microsoft has a patch for it. I run Windows update and
> there are no updates available for my system. Windows ME.
> I then check my install history for updates and the patch
> for this Sasser MS835732 does not show as being installed.
>
> I have Works Suite 2000.
>
> Should I manually install this patch or just forget about
> it. I don't appear to be infected.
>
> Thanks

http://securityresponse.symantec.com/avcenter/venc/data/w32.sasser.b.worm.html

g-w

White
Wed May 05 12:09:08 CDT 2004

If you are going to www.windowsupdate.microsoft.com and
expecting an update with the title "SASSER PATCH," it
doesn't work that way.

It is my understanding that Sasser is exploiting a known
Windows flaw for which Microsoft issued a software patch
three weeks ago. What the flaw was or what patch fixed it
three weeks ago, I do not know the specifics of that.
Sasser is exploiting a particular flaw; the patch three
weeks ago fixed that flaw. The creator(s) of Sasser
noticed the flaw probably before Microsoft fixed it,
created it, and then unleashed it for those users who
never bother updating Windows.

Understand?

zz
Wed May 05 12:13:52 CDT 2004

Ron wrote:
> I read alot about this Vasser worm or virus and that
> Microsoft has a patch for it. I run Windows update and
> there are no updates available for my system. Windows ME.
> I then check my install history for updates and the patch
> for this Sasser MS835732 does not show as being installed.
>
> I have Works Suite 2000.
>
> Should I manually install this patch or just forget about
> it. I don't appear to be infected.
>
> Thanks

W32.Sasser.B.Worm can run on, but not infect, Windows 95/98/Me computers.

http://securityresponse.symantec.com/avcenter/venc/data/w32.sasser.b.worm.html

g-w

White
Wed May 05 13:04:42 CDT 2004

>-----Original Message-----
>W32.Sasser.B.Worm can run on, but not infect, Windows
>95/98/Me computers.

Why not include the whole thing? "W32.Sasser.B.Worm
[Sasser] can run on, but not infect, Windows 95/98/Me
computers. Although these operating systems cannot be
infected, [THEY CAN STILL BE USED] to infect the
vulnerable systems to which they are able to connect. In
this case, the worm will waste a lot of resources so that
programs cannot properly run, including [Symantec's]
removal tool. (On Windows 95/98/Me computers, the tool
should be run in Safe mode.)"

Radials
Wed May 05 17:27:24 CDT 2004

Hey, white walls. You're showing your lack of knowledge.
You should have just told the user that, since Win ME is
not affected by the LSASS vulnerability, there is no patch
to install. (There indeed is not) Instead, you
sarcastically attack someone who has no more knowledge
than yourself, but actually KNOWS it, adn is just asking
for help.

What are your qualifications? Why don't you leave the
help to certified people here who 1. know what they are
doing and 2. want to help.
>-----Original Message-----
>If you are going to www.windowsupdate.microsoft.com and
>expecting an update with the title "SASSER PATCH," it
>doesn't work that way.
>
>It is my understanding that Sasser is exploiting a known
>Windows flaw for which Microsoft issued a software patch
>three weeks ago. What the flaw was or what patch fixed it
>three weeks ago, I do not know the specifics of that.
>Sasser is exploiting a particular flaw; the patch three
>weeks ago fixed that flaw. The creator(s) of Sasser
>noticed the flaw probably before Microsoft fixed it,
>created it, and then unleashed it for those users who
>never bother updating Windows.
>
>Understand?
>.
>

Radials
Wed May 05 17:31:21 CDT 2004

Whitewalls, again, showing your sarcasm and lack of
knowledge.

They are just saying that it will run on 95/98ME to cover
their tracks. If these OS's cannot be infected over the
internet, the only way to run Sasser on them is by
manually installing it, sinse (as of yet) it also does not
prpogate via network shares.

What's your point? Are you worried that people are going
to find the Sasser exe files on an infected machine,
manually shuttle them to an Win 98 box, and run them to
see what happens?
>-----Original Message-----
>>-----Original Message-----
>>W32.Sasser.B.Worm can run on, but not infect, Windows
>>95/98/Me computers.
>
>Why not include the whole thing? "W32.Sasser.B.Worm
>[Sasser] can run on, but not infect, Windows 95/98/Me
>computers. Although these operating systems cannot be
>infected, [THEY CAN STILL BE USED] to infect the
>vulnerable systems to which they are able to connect. In
>this case, the worm will waste a lot of resources so that
>programs cannot properly run, including [Symantec's]
>removal tool. (On Windows 95/98/Me computers, the tool
>should be run in Safe mode.)"
>.
>

Ron
Fri May 07 18:13:43 CDT 2004

Hey Radials, nice going. I thought he was a bit out of
line myself but just chose to ignore him. After reading
more about it I found it didn't apply to my system anyway.
Thanks
Ron....

>-----Original Message-----
>Hey, white walls. You're showing your lack of
knowledge.
>You should have just told the user that, since Win ME is
>not affected by the LSASS vulnerability, there is no
patch
>to install. (There indeed is not) Instead, you
>sarcastically attack someone who has no more knowledge
>than yourself, but actually KNOWS it, adn is just asking
>for help.
>
>What are your qualifications? Why don't you leave the
>help to certified people here who 1. know what they are
>doing and 2. want to help.
>>-----Original Message-----
>>If you are going to www.windowsupdate.microsoft.com and
>>expecting an update with the title "SASSER PATCH," it
>>doesn't work that way.
>>
>>It is my understanding that Sasser is exploiting a known
>>Windows flaw for which Microsoft issued a software patch
>>three weeks ago. What the flaw was or what patch fixed
it
>>three weeks ago, I do not know the specifics of that.
>>Sasser is exploiting a particular flaw; the patch three
>>weeks ago fixed that flaw. The creator(s) of Sasser
>>noticed the flaw probably before Microsoft fixed it,
>>created it, and then unleashed it for those users who
>>never bother updating Windows.
>>
>>Understand?
>>.
>>
>.
>