Updating ICF, or otherwise protecting agains w32.blaster.worm

[Naomi Magen]

Hi,
I was surprised not to find a question like this already.

We have a network box in the field using XP Embeded (not SP1). I assume it
is vulnerable to the latest worm (w32.blaster.worm), like all XP systems
that do not have the latest security patch.

Is adding an entry to ICF that blocks port 132 enough? If not, is there a
patch for XP Embedded (I didn't find one in any of the locations that dealt
with the problem).

Thanks,

Naomi Magen
TMT Coaxial Networks
(e-mail address removed)

 

[Herbert Reichardt]

Hi,
How can we easily fix that very critical bug at our customers XP
embedded systems in the field?
Building a new image only to deploy 3 new files is not an option,
and the standard update for XP (WindowsXP-KB823980-x86-ENU.exe) doesnt
work. Why doesn't this simple update work for xp embedded, i think XP
embedded and XP pro use binary identically files ?
That really sucks if we must build a new image for each critical bug fix

Thanks
H. Reichardt

 

[Naomi Magen]

Hi,

Thanks for the pointer. Unfortunately, the QFE requires SP1. As I said, Our
systems are not running SP1. Can this QFE be applied?

Thanks,

Naomi Magen
TMT Coaxial Networks
(e-mail address removed)

 

[Andy Allred [MS]]

I responded to you offline for clarification and to expedite any assistance
you require.

Please start a new thread to bring the subject to the top if you need
anything else.

Thanks

--
Andy

This posting is provided "AS IS" with no warranties, and confers no
rights.
=====================================================