Security Bulletin
Microsoft Security Bulletin MS13-042 - Important
Vulnerabilities in Microsoft Publisher Could Allow Remote Code Execution (2830397)
Published: May 14, 2013
Version: 1.0
General Information
Executive Summary
This security update resolves eleven privately reported vulnerabilities in Microsoft Office. The vulnerabilities could allow remote code execution if a user open a specially crafted Publisher file with an affected version of Microsoft Publisher. An attacker who successfully exploited these vulnerabilities could gain the same user rights as the current user. 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 security update is rated Important for supported editions of Microsoft Publisher 2003, Microsoft Publisher 2007, and Microsoft Publisher 2010. For more information, see the subsection, Affected and Non-Affected Software, in this section.
The security update addresses the vulnerabilities by correcting how Microsoft Publisher parses 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. Customers can configure automatic updating to check online for updates from Microsoft Update by using the Microsoft Update service. Customers who have automatic updating enabled and configured to check online for updates from Microsoft Update typically will not need to take any action because this security update will be downloaded and installed automatically. Customers who have not enabled automatic updating need to check for updates from Microsoft Update and install this update manually. For information about specific configuration options in automatic updating, see Microsoft Knowledge Base Article 294871.
For administrators and enterprise installations, or end users who want to install this security update manually, Microsoft recommends that customers apply the update at the earliest opportunity using update management software, or by checking for updates using the Microsoft Update service.
See also the section, Detection and Deployment Tools and Guidance, later in this bulletin.
Knowledge Base Article
Knowledge Base Article | 2830397 |
---|---|
File information | Yes |
SHA1/SHA2 hashes | Yes |
Known issues | Yes |
Affected and Non-Affected Software
The following software have 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, see Microsoft Support Lifecycle.
Affected Software
Microsoft Office
Microsoft Office Suite and Other Software | Component | Maximum Security Impact | Aggregate Severity Rating | Updates Replaced |
---|---|---|---|---|
Microsoft Office Suites and Components | ||||
Microsoft Office 2003 Service Pack 3 | [Microsoft Publisher 2003 Service Pack 3](https://www.microsoft.com/download/details.aspx?familyid=9b186d45-ace4-44ff-9510-f478b918ec5d) (2810047) | Remote Code Execution | Important | 2553084 in [MS11-091](http://go.microsoft.com/fwlink/?linkid=235287) |
Microsoft Office 2007 Service Pack 3 | [Microsoft Publisher 2007 Service Pack 3](https://www.microsoft.com/download/details.aspx?familyid=8f8af5d3-76b2-4ff8-a35b-e04d3458159f) (2597971) | Remote Code Execution | Important | 2596705 in [MS11-091](http://go.microsoft.com/fwlink/?linkid=235287) |
Microsoft Office 2010 Service Pack 1 (32-bit editions) | [Microsoft Publisher 2010 Service Pack 1 (32-bit editions)](https://www.microsoft.com/download/details.aspx?familyid=2524228d-5e6f-4520-b18b-668309e71a9d) (2553147) | Remote Code Execution | Important | None |
Microsoft Office 2010 Service Pack 1 (64-bit editions) | [Microsoft Publisher 2010 Service Pack 1 (64-bit editions)](https://www.microsoft.com/download/details.aspx?familyid=bc3bedf6-9ee1-4de5-a6e4-cb92cbb16acc) (2553147) | Remote Code Execution | Important | None |
Office and Other Software |
---|
Microsoft Publisher 2013 (32-bit editions) |
Microsoft Publisher 2013 (64-bit editions) |
Update FAQ
Why does this update address several reported security vulnerabilities?
This update contains support for several vulnerabilities because the modifications that are required to address these issues are located in related files.
How are Microsoft Office standalone programs affected by the vulnerabilities?
A Microsoft Office standalone program is affected with the same severity rating as the corresponding component in a Microsoft Office Suite. For example, a standalone installation of Microsoft Publisher is affected with the same severity rating as an installation of Microsoft Publisher that was delivered with a Microsoft Office Suite.
The Microsoft Office component discussed in this article is part of the Microsoft Office Suite that I have installed on my system; however, I did not choose to install this specific component. Will I be offered this update?
Yes, if the component discussed in this bulletin was delivered with the version of the Microsoft Office Suite installed on your system, the system will be offered updates for it whether the component is installed or not. The detection logic used to scan for affected systems is designed to check for updates for all components that were delivered with the particular Microsoft Office Suite and to offer the updates to a system. Users who choose not to apply an update for a component that is not installed, but is delivered with their version of the Microsoft Office Suite, will not increase the security risk of that system. On the other hand, users who do choose to install the update will not have a negative impact on the security or performance of a system.
Does the offer to update a non-vulnerable version of Microsoft Office constitute an issue in the Microsoft update mechanism?
No. The update mechanism is functioning correctly in that it detects a product version for the applicable software on the system that is within the range of product versions that the update applies to and thus, offers the update.
I am using an older release of the software discussed in this security bulletin. What should I do?
The affected software listed in this bulletin have been tested to determine which releases are affected. Other releases are past their support life cycle. For more information about the product lifecycle, see the Microsoft Support Lifecycle website.
It should be a priority for customers who have older releases of the software to migrate to supported releases to prevent potential exposure to vulnerabilities. To determine the support lifecycle for your software release, see Select a Product for Lifecycle Information. For more information about service packs for these software releases, see Service Pack Lifecycle Support Policy.
Customers who require custom support for older software must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, see the Microsoft Worldwide Information website, select the country in the Contact Information list, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Microsoft Support Lifecycle Policy FAQ.
Vulnerability Information
Severity Ratings and Vulnerability Identifiers
The following severity ratings assume the potential maximum impact of the vulnerability. For information regarding the likelihood, within 30 days of this security bulletin's release, of the exploitability of the vulnerability in relation to its severity rating and security impact, please see the Exploitability Index in the May bulletin summary. For more information, see Microsoft Exploitability Index.
Table: Part 1 (continued below in Part 2)
Affected Software | Publisher Negative Value Allocation Vulnerability - CVE-2013-1316 | Publisher Integer Overflow Vulnerability - CVE-2013-1317 | Publisher Corrupt Interface Pointer Vulnerability - CVE-2013-1318 | Publisher Return Value Handling Vulnerability - CVE-2013-1319 | Publisher Buffer Overflow Vulnerability - CVE-2013-1320 | Publisher Return Value Validation Vulnerability - CVE-2013-1321 |
---|---|---|---|---|---|---|
Microsoft Publisher 2003 Service Pack 3 | Important Remote Code Execution |
Important Remote Code Execution |
Important Remote Code Execution |
Important Remote Code Execution |
Important Remote Code Execution |
Important Remote Code Execution |
Microsoft Publisher 2007 Service Pack 3 | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable |
Microsoft Publisher 2010 Service Pack 1 (32-bit editions) | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable |
Microsoft Publisher 2010 Service Pack 1 (64-bit editions) | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable |
Affected Software | Publisher Invalid Range Check Vulnerability - CVE-2013-1322 | Publisher Incorrect NULL Value Handling Vulnerability - CVE-2013-1323 | Publisher Signed Integer Vulnerability - CVE-2013-1327 | Publisher Pointer Handling Vulnerability - CVE-2013-1328 | Publisher Buffer Underflow Vulnerability - CVE-2013-1329 | Aggregate Severity Rating |
---|---|---|---|---|---|---|
Microsoft Publisher 2003 Service Pack 3 | Important Remote Code Execution |
Important Remote Code Execution |
Important Remote Code Execution |
Important Remote Code Execution |
Important Remote Code Execution |
Important |
Microsoft Publisher 2007 Service Pack 3 | Not applicable | Not applicable | Not applicable | Important Remote Code Execution |
Not applicable | Important |
Microsoft Publisher 2010 Service Pack 1 (32-bit editions) | Not applicable | Not applicable | Not applicable | Important Remote Code Execution |
Not applicable | Important |
Microsoft Publisher 2010 Service Pack 1 (64-bit editions) | Not applicable | Not applicable | Not applicable | Important Remote Code Execution |
Not applicable | Important |
Security update file name | For Microsoft Publisher 2003: office2003-kb2810047-fullfile-enu.exe |
Installation switches | See Microsoft Knowledge Base Article 912203 |
Restart requirement | In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. |
Removal information | Use Add or Remove Programs item in Control Panel. Note When you remove this update, you may be prompted to insert the Microsoft Office 2003 CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs item in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771. |
File information | See Microsoft Knowledge Base Article 2810047 |
Registry key verification | Not applicable |
Security update file name | For Microsoft Publisher 2007: publisher2007-kb2597971-fullfile-x86-glb.exe |
Installation switches | See Microsoft Knowledge Base Article 912203 |
Restart requirement | In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. |
Removal information | Use Add or Remove Programs item in Control Panel. |
File information | See Microsoft Knowledge Base Article 2597971 |
Registry key verification | Not applicable |
Security update file name | For Microsoft Publisher 2010 (32-bit editions): publisher2010-kb2553147-fullfile-x86-glb.exe |
For Microsoft Publisher 2010 (64-bit editions): publisher2010-kb2553147-fullfile-x64-glb.exe |
|
Installation switches | See Microsoft Knowledge Base Article 912203 |
Restart requirement | In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. |
Removal information | Use Add or Remove Programs item in Control Panel. |
File information | See Microsoft Knowledge Base Article 2553147 |
Registry key verification | Not applicable |