SANS ISC: November 2010 Microsoft Black Tuesday Summary - Internet Security | DShield

• SANS Site Network
  • Current Site
  • Internet Storm Center
  • Other SANS Sites Help
  • Graduate Degree Programs
  • Security Training
  • Security Certification
  • Security Awareness Training
  • Penetration Testing
  • Industrial Control Systems
  • Cyber Defense Foundations
  • DFIR
  • Software Security
  • Government OnSite Training

SANS ISC InfoSec Forums

Anyone having difficulty installing the Office 2010 patch for Windows Vista 32-bit? It downloads, tries to install, and Windows Update immediately says code 80200053, unknown error after it tries to install it. It got the other patches (well, the November malicious software tool) and that "installed" fine. A reboot didn't solve it as I tried again to download/install the Office patch afterwards.

Never mind. After 4 tries, it finally went through. Sheesh.

Would it be practical to include (as a separate table within the same monthly article) a listing of current Adobe and Quicktime products with this monthly publication?

I know the non-MS update cycles do not match the MS cycle. I wish they did, since it could mean doing all my testing once a month.

Putting the info into a single place each month (allowing for out-of-band events) would give us a centralized place to check to ensure we didn't miss something since the last Black Tuesday announcement.

A point to consider may be that there would need to be a limit to the number of products included in such a revision. If adding Adobe stuff is ok, would adding Quicktime be too much?

Perhaps a test for inclusion might be whether or not the "general population" would be affected by a specific product update. For example, how many would be affected by Acrobat updates but not care about Photoshop, AutoCAD, etc?

Anyone else have any thoughts? Myself, I am so appreciative for what ISC does as it is that I'm not going to squawk if nothing changes, but can see how this would be an improvement (at least, for me it would be.)

:)

Win7 x64: The office patches installed fine, but I had problems with 80200053 on the November MSRT download. Multiple tries got it to install. Note: There are new silent errors this month such as ->Scan ERROR: resource process://pid:5240 (code 0x00000005 (5)) . One of these processes is the Windows audiodg.exe. Manually downloading and running MSRT results in the same error. (in \windows\debug\mrt.log)

I agree with Joel that it would be great to have a central list of common software and the current patch level. I also agree that with all the good work the ISC handlers already do I would hate to add more work to them.

If this is something that could be easily done and not add to the already busy work day for the handlers I would be all for it.

Thanks again to all the handlers and their continued efforts to keep us safe.

Microsoft delayed patches for Mac OS X Office 2004 and 2008 by at least one month, according to Computerworld.com.

Yet somehow Microsoft had the resources to patch Mac OS X Office 2011, released 16 days ago.

I don't know about the complete goodness of Secunia's PSI, but it seems to catch things at what is for me, an acceptable low lag time on Java and Adobe patches. The new 2.0xx versions also offer automagical patching on several applications.