Microsoft announced yesterday that they will be releasing an out of cycle critical patch to handle a remote code execution problem today. At this point it is not clear what the affected software is are:

  1. Microsoft Windows 2000 Service Pack 4 (Critical)
  2. Windows XP Service Pack 2 and Windows XP Service Pack 3 (Critical)
  3. Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 (Critical)
  4. Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 (Critical)
  5. Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 (Critical)
  6. Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems (Critical)
  7. Windows Vista and Windows Vista Service Pack 1 (Important)
  8. Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1 (Important)
  9. Windows Server 2008 for 32-bit Systems* (Important)
  10. Windows Server 2008 for x64-based Systems*
  11. Windows Server 2008 for Itanium-based Systems

*Windows Server 2008 server core installation affected. For supported editions of Windows Server 2008, this update applies, with the same severity rating, whether or not Windows Server 2008 was installed using the Server Core installation option. For more information on this installation option, see Server Core. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008; see Compare Server Core Installation Options.

A reboot will be required

$joke

I’ll be sure to update this once I find out more information.

Article Link

UPDATE: Word is filtering in that today’s Microsoft patch will be a huge deal. It will be a ‘critical’ on Windows 2000, Windows XP and Windows Server 2003.

UPDATE 2: Microsoft Security Bulletin MS08-067 – Critical, has now been posted on their site.

UPDATE 3: And from the Microsoft Security Vulnerability Research & Defense blog: More detail about MS08-067, the out-of-band netapi32.dll security update. (via @securitytwits)

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.