3rd WMF one in 4 months

Furthermore you can explicitly configure permissions to deny & log read/exec access to shimgvw.dll system wide or on per application basis. This is functionally equivalent to Microsoft's suggested workaround of unregistering the DLL but the advantage is t

# random size; # no .wmf extension, (.jpg), but could be any other image extension actually; # a random piece of junk in front of the bad call; carefully crafted to be larger than the MTU on an ethernet network; # a number of possible calls to run the

"We have received multiple reports from the Netherlands about an IM-Worm which spreads via MSN using..."