__________________________________________________________ The U.S. Department of Energy Computer Incident Advisory Capability ___ __ __ _ ___ / | /_\ / \___ __|__ / \ \___ __________________________________________________________ INFORMATION BULLETIN Vulnerabilities in Microsoft Office Publisher [Microsoft Security Bulletin (MS08-012)] February 13, 2008 13:00 GMT Number S-178 [REVISED 15 Feb 2008] ______________________________________________________________________________ PROBLEM: A remote code execution vulnerability exists in the way Microsoft Office Publisher validates application data when loading Publisher files to memory and memory index values. PLATFORM: Publisher 2000, 2002, 2003 (all editions) DAMAGE: Remote code execution. SOLUTION: Upgrade to the appropriate version. ______________________________________________________________________________ VULNERABILITY The risk is MEDIUM. An attacker could exploit the vulnerability ASSESSMENT: by constructing a specially crafted Publisher (.pub) file. When a user views the .pub file, the vulnerability could allow remote code execution. An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. ______________________________________________________________________________ LINKS: CIAC BULLETIN: http://www.ciac.org/ciac/bulletins/s-178.shtml ORIGINAL BULLETIN: http://www.microsoft.com/technet/security/Bulletin/MS08-012.mspx CVE: http://www.cve.mitre.org/cgi-bin/cvename.cgi?name= CVE-2008-0102 CVE-2008-0104 ______________________________________________________________________________ REVISION HISTORY: 02/15/2008 - revised S-178 to reflect changes Microsoft has made in MS08-012 where they updated to reflect that there are no known issues with installing this security update, and to list Microsoft Publisher 2003 Service Pack 2 (instead of Service Pack 3) in the MBSA and SMS tables under Detection and Deployment. [***** Start Microsoft Security Bulletin (MS08-012) *****] Microsoft Security Bulletin MS08-012 - Critical Vulnerabilities in Microsoft Office Publisher Could Allow Remote Code Execution (947085) Published: February 12, 2008 | Updated: February 13, 2008 Version: 1.1 General Information Executive Summary This critical security update resolves two privately reported vulnerabilities in Microsoft Office Publisher that could allow remote code execution if a user opens a specially crafted Publisher file. An attacker who successfully exploited these vulnerabilities could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. This is a critical security update for supported releases of Microsoft Office Publisher 2000; supported releases of Microsoft Office Publisher 2002; and supported editions of Microsoft Office Publisher 2003 Service Pack 2. Microsoft Publisher 2003 Service Pack 3, Microsoft Office Publisher 2007, and Microsoft Office Publisher 2007 Service Pack 1 are not impacted by this vulnerability. For more information, see the subsection, Affected and Non-Affected Software, in this section. This security update addresses the vulnerabilities by modifying the way that Microsoft Office Publisher handles specially crafted Publisher files. For more information about the vulnerabilities, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information. Recommendation. Microsoft recommends that customers should apply the update immediately. Known Issues. Microsoft Knowledge Base Article 947085 documents the currently known issues that customers may experience when they install this security update. The article also documents recommended solutions for these issues Top of section Affected and Non-Affected Software The software listed here has been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle. Affected Software Office Suite and Other Affected Software Component Maximum Security Impact Aggregate Severity Rating Bulletins Replaced by This Update Microsoft Office 2000 Service Pack 3 Microsoft Office Publisher 2000 (KB946255) Remote Code Execution Critical MS06-054 Microsoft Office XP Service Pack 3 Microsoft Office Publisher 2002 (KB946216) Remote Code Execution Important MS06-054 Microsoft Office 2003 Service Pack 2 Microsoft Office Publisher 2003 Service Pack 2 (KB946254) Remote Code Execution Important MS06-054 Non-Affected Software Office Suite Application 2007 Microsoft Office System Microsoft Office Publisher 2007 2007 Microsoft Office System Service Pack 1 Microsoft Office Publisher 2007 Service Pack 1 Microsoft Office 2003 Service Pack 3 Microsoft Office Publisher 2003 Service Pack 3 Vulnerability Information Severity Ratings and Vulnerability Identifiers Vulnerability Severity Rating and Maximum Security Impact by Affected Software Affected Software Publisher Invalid Memory Reference Vulnerability – CVE-2008-0102 Publisher Memory Corruption Vulnerability – CVE-2008-0104 Aggregate Severity Rating Microsoft Publisher 2000 Service Pack 3 Critical Remote Code Execution Critical Remote Code Execution Critical Microsoft Publisher 2002 Service Pack 3 Important Remote Code Execution Important Remote Code Execution Important Microsoft Publisher 2003 Service Pack 2 Important Remote Code Execution Important Remote Code Execution Important Publisher Invalid Memory Reference Vulnerability – CVE-2008-0102 A remote code execution vulnerability exists in the way Microsoft Office Publisher validates application data when loading Publisher files to memory. An attacker could exploit the vulnerability by constructing a specially crafted Publisher (.pub) file. When a user views the .pub file, the vulnerability could allow remote code execution. An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2008-0102. Publisher Memory Corruption Vulnerability – CVE-2008-0104 A remote code execution vulnerability exists in the way Microsoft Office Publisher validates memory index values. An attacker could exploit the vulnerability by constructing a specially crafted Publisher (.pub) file. When a user views the .pub file, the vulnerability could allow remote code execution. An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2008-0102. Update Information Detection and Deployment Tools and Guidance Manage the software and security updates you need to deploy to the servers, desktop, and mobile systems in your organization. For more information see the TechNet Update Management Center. The Microsoft TechNet Security Web site provides additional information about security in Microsoft products. Security updates are available from Microsoft Update, Windows Update, and Office Update. Security updates are also available from the Microsoft Download Center. You can find them most easily by doing a keyword search for "security update." Finally, security updates can be downloaded from the Microsoft Update Catalog. The Microsoft Update Catalog provides a searchable catalog of content made available through Windows Update and Microsoft Update, including security updates, drivers and service packs. By searching using the security bulletin number (such as, “MS07-036”), you can add all of the applicable updates to your basket (including different languages for an update), and download to the folder of your choosing. For more information about the Microsoft Update Catalog, see the Microsoft Update Catalog FAQ. Detection and Deployment Guidance Microsoft has provided detection and deployment guidance for this month’s security updates. This guidance will also help IT professionals understand how they can use various tools to help deploy the security update, such as Windows Update, Microsoft Update, Office Update, the Microsoft Baseline Security Analyzer (MBSA), the Office Detection Tool, Microsoft Systems Management Server (SMS), and the Extended Security Update Inventory Tool. For more information, see Microsoft Knowledge Base Article 910723. Microsoft Baseline Security Analyzer Microsoft Baseline Security Analyzer (MBSA) allows administrators to scan local and remote systems for missing security updates as well as common security misconfigurations. For more information about MBSA visit Microsoft Baseline Security Analyzer Web site. The following table provides the MBSA detection summary for this security update. Software MBSA 2.0.1 Microsoft Publisher 2000 Service Pack 3 No Microsoft Publisher 2002 Service Pack 3 Yes Microsoft Publisher 2003 Service Pack 2 Yes For more information about MBSA 2.0.1, see MBSA 2.0 Frequently Asked Questions. Note For customers using legacy software not supported by MBSA 2.0.1, Microsoft Update, and Windows Server Update Services: please visit Microsoft Baseline Security Analyzer and reference the Legacy Product Support section on how to create comprehensive security update detection with legacy tools. Windows Server Update Services By using Windows Server Update Services (WSUS), administrators can deploy the latest critical updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000 to Windows 2000 and later operating systems. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. Systems Management Server The following table provides the SMS detection and deployment summary for this security update. Software SMS 2.0 SMS 2003 with SUSFP SMS2003 with ITMU SCCM 2007 Microsoft Publisher 2000 Service Pack 3 Yes Yes No Yes Microsoft Publisher 2002 Service Pack 3 Yes Yes Yes Yes Microsoft Publisher 2003 Service Pack 2 Yes Yes Yes Yes For SMS 2.0 and SMS 2003, the SMS SUS Feature Pack (SUSFP), which includes the Security Update Inventory Tool (SUIT), can be used by SMS to detect security updates. See also Downloads for Systems Management Server 2.0. For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, see SMS 2003 Inventory Tool for Microsoft Updates. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications. For more information about the Office Inventory Tool and other scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003. System Center Configuration Manager (SCCM) 2007 uses WSUS 3.0 for detection of updates. For more information about SCCM 2007 Software Update Management, visit System Center Configuration Manager 2007. For more information about SMS, visit the SMS Web site. For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles. Note If you have used an Administrative Installation Point (AIP) for deploying Office 2000, Office XP or Office 2003, you may not be able to deploy the update using SMS if you have updated the AIP from the original baseline. For more information, see the Office Administrative Installation Point heading in this section. Office Administrative Installation Point If you installed your application from a server location, the server administrator must update the server location with the administrative update and deploy that update to your system. • For supported versions of Microsoft Office 2000, see How to Create an Administrative Installation Point. For more information about how to change the source for a client system from an updated administrative installation point to an Office 2000 original baseline source or Service Pack 3 (SP3), see Microsoft Knowledge Base Article 932889. Note. If you plan to manage software updates centrally from an updated administrative image, you can find more information in the article Updating Office 2000 Clients from a Patched Administrative Image. • For supported versions of Microsoft Office XP, see Creating an Administrative Installation Point. For more information on how to change the source for a client system from an updated administrative installation point to an Office XP original baseline source or Service Pack 3 (SP3), see Microsoft Knowledge Base Article 922665. Note. If you plan to manage software updates centrally from an updated administrative image, you can find more information in the article Updating Office XP Clients from a Patched Administrative Image. • For supported versions of Microsoft Office 2003, see Creating an Administrative Installation Point. If you have an Administrative Installation Point with a non-supported version of Microsoft Office 2003, see Microsoft Knowledge Base Article 902349. Note. If you plan to manage software updates centrally from an updated administrative image, you can find more information in the article Distributing Office 2003 Product Updates. • For supported versions of the 2007 Microsoft Office System, see Create a network installation point for the 2007 Office System. Note. If you plan to manage security updates centrally use Windows Server Update Services. For more information about how to deploy security updates for the 2007 Microsoft Office System using Windows Server Update Services, visit the Windows Server Update Services Web site. Security Update Deployment Affected Software For information about the specific security update for your affected software, click the appropriate link: * Publisher 2000 (all editions) * Publisher 2002 (all editions) * Publisher 2003 (all editions) Other Information Acknowledgments Microsoft thanks the following for working with us to help protect customers: • Piotr Bania for reporting the Publisher Invalid Memory Reference Vulnerability - CVE-2008-0102. • Bing Liu of Fortinet Security Research for reporting the Publisher Invalid Memory Reference Vulnerability - CVE-2008-0102. • Bing Liu of Fortinet Security Research for reporting the Publisher Memory Corruption Vulnerability - CVE-2008-0104. Top of section Support • Customers in the U.S. and Canada can receive 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 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 the International Support Web site. Top of section 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. Top of section Revisions • V1.0 (February 12, 2007): Bulletin published. • V1.1 (February 13, 2008): Bulletin updated to reflect that there are no known issues with installing this security update, and to list Microsoft Publisher 2003 Service Pack 2 (instead of Service Pack 3) in the MBSA and SMS tables under Detection and Deployment. [***** End Microsoft Security Bulletin (MS08-012) *****] _______________________________________________________________________________ CIAC wishes to acknowledge the contributions of Microsoft for the information contained in this bulletin. _______________________________________________________________________________ CIAC, the Computer Incident Advisory Capability, is the computer security incident response team for the U.S. Department of Energy (DOE) and the emergency backup response team for the National Institutes of Health (NIH). CIAC is located at the Lawrence Livermore National Laboratory in Livermore, California. CIAC is also a founding member of FIRST, the Forum of Incident Response and Security Teams, a global organization established to foster cooperation and coordination among computer security teams worldwide. CIAC services are available to DOE, DOE contractors, and the NIH. CIAC can be contacted at: Voice: +1 925-422-8193 (7x24) FAX: +1 925-423-8002 STU-III: +1 925-423-2604 E-mail: ciac@ciac.org Previous CIAC notices, anti-virus software, and other information are available from the CIAC Computer Security Archive. World Wide Web: http://www.ciac.org/ Anonymous FTP: ftp.ciac.org PLEASE NOTE: Many users outside of the DOE, ESnet, and NIH computing communities receive CIAC bulletins. If you are not part of these communities, please contact your agency's response team to report incidents. Your agency's team will coordinate with CIAC. The Forum of Incident Response and Security Teams (FIRST) is a world-wide organization. A list of FIRST member organizations and their constituencies can be obtained via WWW at http://www.first.org/. This document was prepared as an account of work sponsored by an agency of the United States Government. Neither the United States Government nor the University of California nor any of their employees, makes any warranty, express or implied, or assumes any legal liability or responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or process disclosed, or represents that its use would not infringe privately owned rights. Reference herein to any specific commercial products, process, or service by trade name, trademark, manufacturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation or favoring by the United States Government or the University of California. The views and opinions of authors expressed herein do not necessarily state or reflect those of the United States Government or the University of California, and shall not be used for advertising or product endorsement purposes. LAST 10 CIAC BULLETINS ISSUED (Previous bulletins available from CIAC) S-168: net-snmp Vulnerability S-169: Squid Vulnerability S-170: KAME Project IPv6 IPComp Vulnerability S-171: Kernel Security Update S-172: Vulnerability in WebDAV Mini-Redirector S-173: Vulnerability in Internet Information Services S-174: Vulnerability in OLE Automation S-175: Vulnerability in Microsoft Word S-176: Cumulative Security Update for Internet Explorer S-177: Vulnerabilities in Microsoft Works File Converter