Issued: April 13, 2004
Updated: August 10, 2004
Version Number: 3.1
An End User version of this advisory is available by visiting the following Web site.
Protect Your PC: Microsoft has provided information on how you can help protect your PC at the following locations:
| • | End Users can visit the Protect Your PC Web site. |
| • | IT Professionals can visit the IT Pro TechNet Security Information Web site. |
Update Management Strategies: The Microsoft Guide to Security Patch Management Web site provides additional information about Microsoft's best practice recommendations for applying security updates.
IT Pro Security Zone Community: Learn to improve security and optimize your IT infrastructure, and participate with other IT Pros on security topics in the IT Pro Security Zone Web site.
Microsoft Security Notification Service: To receive automatic e-mail notifications whenever Microsoft security bulletins are issued, subscribe to the Microsoft Security Notification Service.
Included in this advisory are updates for the newly discovered vulnerabilities in Microsoft Windows. These vulnerabilities, broken down by severity are:
Critical
Microsoft Security Bulletin MS04-011 – Security Update for Microsoft Windows (835732)
Affected Software |
| ||||||||||||||||||||||
Impact | Remote Code Execution | ||||||||||||||||||||||
Last Revised | August 10, 2004 | ||||||||||||||||||||||
Version Number | 2.1 |
Microsoft Security Bulletin MS04-012 – Cumulative Update for Microsoft RPC/DCOM (828741)
Affected Software |
| ||||||||||||||||||||
Impact | Remote Code Execution | ||||||||||||||||||||
Last Revised | April 21, 2004 | ||||||||||||||||||||
Version Number | 1.1 |
Microsoft Security Bulletin MS04-013 – Cumulative Security Update for Outlook Express (837009)
Affected Software |
| ||||||||||||||||||||
Impact | Remote Code Execution | ||||||||||||||||||||
Last Revised | April 13, 2004 | ||||||||||||||||||||
Version Number | 1.0 |
Important
Affected Software |
| ||||||||||||||||||||
Impact | Remote Code Execution | ||||||||||||||||||||
Last Revised | May 11, 2004 | ||||||||||||||||||||
Version Number | 2.0 |
Software Update Services (SUS):
Microsoft Software Update Services (SUS) enables administrators to quickly and reliably deploy the latest critical updates and security updates to Windows® 2000 and Windows Server™ 2003-based servers, as well as to desktop systems running Windows 2000 Professional or Windows XP Professional.
For information about how to deploy this security update with Software Update Services, visit the Software Update Services Web site.
Systems Management Server (SMS):
Systems Management Server can provide assistance deploying this security update. For information about Systems Management Server visit the SMS Web Site. For detailed information about the many enhancements to the security update deployment process that SMS 2003 provides, please visit the SMS 2003 Security Patch Management Web site. For users of SMS 2.0, it also provides several additional tools to assist administrators in the deployment of security updates such as the SMS 2.0 Software Update Services Feature Pack and the SMS 2.0 Administration Feature Pack. The SMS 2.0 Software Update Services Feature Pack utilizes the Microsoft Baseline Security Analyzer and the Microsoft Office Detection Tool to provide broad support for security bulletin remediation. Some software updates may require administrative rights following a restart of the computer
Note: The inventory capabilities of the SMS 2.0 Software Update Services Feature Pack may be used for targeting updates to specific computers, and the SMS 2.0 Administration Feature Pack's Elevated Rights Deployment Tool can be used for installation. This provides optimal deployment for updates that require explicit targeting using Systems Management Server and administrative rights after the computer has been restarted.
QChain.exe and Update.exe:
Microsoft has released a command-line tool named QChain.exe that gives system administrators the ability to safely chain security updates together. Chaining is when you install multiple updates without rebooting between each install. Update.exe, used in the updates described in this advisory, has chaining functionality built in. For customers using Windows 2000 Service Pack 2 or higher, Windows XP, or Windows Server 2003, Qchain.exe is not required to chain these updates. Qchain.exe still supports chaining these Windows Updates so that an administrator can create a consistent deployment script across all platforms. For more information on Qchain, visit this Web site
Microsoft Baseline Security Analyzer (MBSA):
The Microsoft Baseline Security Analyzer allows administrators to scan local and remote systems for missing security updates as well as common security misconfigurations. More information on MBSA is available at the Microsoft Baseline Security Analyzer Web site.
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
| • | Carlos Sarraute of Core Security Technologies for reporting the LDAP Vulnerability (CAN-2003-0663). |
| • | Internet Security Systems for reporting the PCT Vulnerability (CAN-2003-0719). |
| • | Ondrej Sevecek for reporting the Winlogon Vulnerability (CAN-2003-0806). |
| • | iDefense and Jouko Pynnönen for reporting the Help and Support Vulnerability (CAN-2003-0907). |
| • | Brett Moore of Security-Assessment.com, Cesar Cerrudo, and Ben Pryor for reporting the Utility Manager Vulnerability (CAN-2003-0908). |
| • | Erik Kamphuis of LogicaCMG working on behalf of the Dutch Tax Office for reporting the Windows Management Vulnerability (CAN-2003-0909). |
| • | NSFOCUS Security Team for reporting the Negotiate SSP Vulnerability (CAN-2004-0119). |
| • | John Lampe of Tenable Network Security for reporting the SSL Vulnerability (CAN-2004-0120) |
| • | Foundstone labs and Qualys for reporting the ASN.1 'Double Free' Vulnerability (CAN-2004-0123). |
| • | eEye Digital Security for reporting the LSASS Vulnerability (CAN-2003-0533), Metafile Vulnerability (CAN-2003-0906), Local Descriptor Table Vulnerability (CAN-2003-0910), Virtual DOS Machine Vulnerability (CAN-2004-0118), RPC Runtime Library Vulnerability (CAN-2003-0813) and the RPCSS Service Vulnerability (CAN-2004-0116). |
| • | Qualys for reporting the CIS – RPC over HTTP Vulnerability (CAN-2003-0807). |
| • | Todd Sabin of BindView for reporting the Object Identity Vulnerability (CAN-2004-0124). |
| • | Matt Thompson of Aberdeen IT for reporting the Jet Vulnerability (CAN-2004-0197) |
Obtaining other security updates:
Updates for other security issues are available from the following locations:
| • | Security updates are available from the Microsoft Download Center: you can find them most easily by doing a keyword search for “security_patch”. |
| • | Updates for consumer platforms are available from the Windows Update Web site. |
Support:
| • | Customers in the U.S. and Canada can get technical support from Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates. |
| • | International customers can get support from their local Microsoft subsidiaries. There is no charge for support associated with security updates. For more information on how to contact Microsoft for support issues, visit the International Support Web site. |
Security Resources:
| • | The Microsoft TechNet Security Web site provides additional information about security in Microsoft products. |
| • | |
| • | |
| • | |
| • | Windows Update Catalog: For more information about the Windows Update Catalog, see Microsoft Knowledge Base Article 323166. |
| • |
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 (April 13, 2004): Bulletin published |
| • | V1.1 (April 21, 2004): Revised to reflect updates that are documented in MS04-011 and MS04-012. |
| • | V1.2 April 28, 2004: Version changed to reflect the updated Caveats section within MS04-011. |
| • | V1.3 May 4, 2004: Version changed to reflect the updated Workaround section within MS04-011. |
| • | V2.0 May 11, 2004: Announcement of a revised version of the Windows XP security update for MS04-014. |
| • | V3.0 June 15, 2004: Version changed to reflect a revised version of the Pan Chinese Windows NT 4.0 Workstation security update for MS04-011. |
| • | V3.1 August 10, 2004: Version changed to reflect a revised Workaround section within MS04-011. |