Australia's Leading Computer Emergency Response Team

To Patch or Not to Patch
Date: 15 August 2008
Original URL: http://www.auscert.org.au/render.html?cid=7066&it=9731

Greetings,

I am sure you are all expecting me to mention something about Microsoft and how you should patch your systems now. And then I would go on to say how you should patch all systems with patches as soon as you can. After all I am a good little security professional.

If you were thinking that then you would be half right. I would definitely recommend patching the Microsoft products. However yesterday you may have seen the "VMware ESX and ESXi Update 2 patch causing error" bulletin we sent. If you didn't read it - basically it caused virtual machines to refuse to power on.

So if you can't patch, and you can't not patch, what do you do? Well testing before deployment is one option. You probably won't be able to test everything, but hopefully it will uncover bugs (like not being able to boot any of your virtual machines) that you would like to avoid introducing into a production environment.

In other news, Symantec Veritas Storage Foundation for Windows has a remote SYSTEM compromise, so you may want to check any systems you run that on are not accessible on TCP port 4888, or apply the patch (after testing of course).

Richard