Microsoft Security Bulletin Summary for December 2010
Published: December 14, 2010
Version: 1.0
This bulletin summary lists security bulletins released for December 2010.
With the release of the security bulletins for December 2010, this bulletin summary replaces the bulletin advance notification originally issued December 9, 2010. For more information about the bulletin advance notification service, see Microsoft Security Bulletin Advance Notification.
For information about how to receive automatic notifications whenever Microsoft security bulletins are issued, visit Microsoft Technical Security Notifications.
Microsoft is hosting a webcast to address customer questions on these bulletins on December 15, 2010, at 11:00 AM Pacific Time (US & Canada). Register now for the December Security Bulletin Webcast. After this date, this webcast is available on-demand. For more information, see Microsoft Security Bulletin Summaries and Webcasts.
Microsoft also provides information to help customers prioritize monthly security updates with any non-security, high-priority updates that are being released on the same day as the monthly security updates. Please see the section, Other Information.
Bulletin Information
Other Information
Microsoft Windows Malicious Software Removal Tool
Microsoft
has released an updated version of the Microsoft Windows Malicious
Software Removal Tool on Windows Update, Microsoft Update, Windows
Server Update Services, and the Download Center.
Non-Security, High-Priority Updates on MU, WU, and WSUS
For information about non-security releases on Windows Update and Microsoft Update, please see:
• | Microsoft Knowledge Base Article 894199: Description of Software Update Services and Windows Server Update Services changes in content. Includes all Windows content. |
• | Updates from Past Months for Windows Server Update Services. Displays all new, revised, and rereleased updates for Microsoft products other than Microsoft Windows. |
Microsoft Active Protections Program (MAPP)
To
improve security protections for customers, Microsoft provides
vulnerability information to major security software providers in
advance of each monthly security update release. Security software
providers can then use this vulnerability information to provide updated
protections to customers via their security software or devices, such
as antivirus, network-based intrusion detection systems, or host-based
intrusion prevention systems. To determine whether active protections
are available from security software providers, please visit the active
protections Web sites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners.
Security Strategies and Community
Update Management Strategies
Security Guidance for Update Management provides additional information about Microsoft’s best-practice recommendations for applying security updates.
Obtaining Other Security Updates
Updates for other security issues are available from the following locations:
IT Pro Security Community
Learn to improve security and optimize your IT infrastructure, and participate with other IT Pros on security topics in IT Pro Security Community.
Security Guidance for Update Management provides additional information about Microsoft’s best-practice recommendations for applying security updates.
Obtaining Other Security Updates
Updates for other security issues are available from the following locations:
• | Security updates are available from Microsoft Download Center. You can find them most easily by doing a keyword search for "security update". |
• | Updates for consumer platforms are available from Microsoft Update. |
• | You can obtain the security updates offered this month on Windows Update, from Download Center on Security and Critical Releases ISO CD Image files. For more information, see Microsoft Knowledge Base Article 913086. |
IT Pro Security Community
Learn to improve security and optimize your IT infrastructure, and participate with other IT Pros on security topics in IT Pro Security Community.
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
• | Aniway of VeriSign iDefense Labs for reporting an issue described in MS10-090 |
• | Nicolas Joly of VUPEN Vulnerability Research Team for reporting an issue described in MS10-090 |
• | Stephen Fewer, working with TippingPoint's Zero Day Initiative, for reporting an issue described in MS10-090 |
• | Peter Vreugdenhil, working with TippingPoint's Zero Day Initiative, for reporting an issue described in MS10-090 |
• | Yosuke Hasegawa for working with us on an issue described in MS10-090 |
• | Jose Antonio Vazquez Gonzalez of VeriSign iDefense Labs for reporting an issue described in MS10-090 |
• | Marc Schoenefeld of the Red Hat Security Response Team, working with the Opera Security Team, for reporting an issue described in MS10-091 |
• | Marc Schoenefeld of the Red Hat Security Response Team for reporting an issue described in MS10-091 |
• | Paul-Kenji Cahier Furuya for reporting an issue described in MS10-091 |
• | Sergey Golovanov, Alexander Gostev, Maxim Golovkin, and Alexey Monastyrsky of Kaspersky Lab, and Vitaly Kiktenko and Alexander Saprykin of Design and Test Lab, for reporting an issue described in MS10-092 |
• | Liam O Murchu of Symantec for reporting an issue described in MS10-092 |
• | Alexandr Matrosov, Eugene Rodionov, Juraj Malcho and David Harley of ESET for reporting an issue described in MS10-092 |
• | Haifei Li of Fortinet's FortiGuard Labs for reporting an issue described in MS10-095 |
• | Simon Raner of ACROS Security for reporting an issue described in MS10-096 |
• | HD Moore of Rapid7 for reporting an issue described in MS10-096 |
• | Muhaimin Dzulfakar of NGS Software for reporting an issue described in MS10-096 |
• | Muhaimin Dzulfakar of NGS Software for reporting an issue described in MS10-097 |
• | Tarjei Mandt of Norman for reporting four issues described in MS10-098 |
• | Stéfan Le Berre of Sysdream for reporting an issue described in MS10-098 |
• | Honggang Ren of Fortinet's FortiGuard Labs for reporting an issue described in MS10-099 |
• | Cesar Cerrudo of Argeniss for reporting an issue described in MS10-100 |
• | Matthias Dieter Wallnöfer and Andrew Bartlett of The Samba Team for reporting an issue described in MS10-101 |
• | HP and techit for reporting an issue described in MS10-102 |
• | Chaouki Bekrar of VUPEN Vulnerability Research Team for reporting five issues described in MS10-103 |
• | Oleksandr Mirosh, working with TippingPoint's Zero Day Initiative, for reporting an issue described in MS10-104 |
• | Yamata Li of Palo Alto Networks for reporting two issues described in MS10-105 |
• | Alin Rad Pop of Secunia Research for reporting an issue described in MS10-105 |
• | Carsten Eiram of Secunia Research for reporting three issues described in MS10-105 |
• | Dyon Balding of Secunia Research for reporting two issues described in MS10-105 |
• | Oleksandr Mirosh, working with TippingPoint's Zero Day Initiative, for reporting an issue described in MS10-106 |
Support
• | The affected software listed have been tested to determine which versions are affected. Other versions are past their support life cycle. To determine the support life cycle for your software version, visit Microsoft Support Lifecycle. |
• | Customers in the U.S. and Canada can receive technical support from Security Support or 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates. For more information about available support options, see Microsoft Help and Support. |
• | International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit International Help and Support. |
Disclaimer
The
information provided in the Microsoft Knowledge Base is provided "as
is" without warranty of any kind. Microsoft disclaims all warranties,
either express or implied, including the warranties of merchantability
and fitness for a particular purpose. In no event shall Microsoft
Corporation or its suppliers be liable for any damages whatsoever
including direct, indirect, incidental, consequential, loss of business
profits or special damages, even if Microsoft Corporation or its
suppliers have been advised of the possibility of such damages. Some
states do not allow the exclusion or limitation of liability for
consequential or incidental damages so the foregoing limitation may not
apply.
Revisions
• | V1.0 (December 14, 2010): Bulletin Summary published. |