Vulnerability in Microsoft Works Could Allow Remote Code Execution (2754670)
Published: October 09, 2012
This security update resolves a privately reported vulnerability in Microsoft Works. The vulnerability could allow remote code execution if a user opens a specially crafted Microsoft Word file using Microsoft Works. An attacker who successfully exploited this vulnerability 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 Microsoft Works 9. For more information, see the subsection, Affected and Non-Affected Software, in this section.
The security update addresses the vulnerability by modifying the way that Microsoft Works converts Word documents. For more information about the vulnerability, 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 in supported editions of Windows XP and Windows Server 2003, see Microsoft Knowledge Base Article 294871. For information about automatic updating in supported editions of Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, see Understanding Windows automatic updating.
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.
Known Issues. None
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.
Frequently Asked Questions (FAQ) Related to This Security Update
**Where are the file information details?**
Refer to the reference tables in the **Security Update Deployment** section for the location of the file information details.
**Where** **are the hashes of the security** **updates?**
The SHA1 and SHA2 hashes of the security updates can be used to verify the authenticity of downloaded security update packages. For the hash information pertaining to this update, see [Microsoft Knowledge Base Article 2754670](http://support.microsoft.com/kb/2754670).
**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](http://go.microsoft.com/fwlink/?linkid=21742) 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](http://go.microsoft.com/fwlink/?linkid=169555). For more information about service packs for these software releases, see [Service Pack Lifecycle Support Policy](http://go.microsoft.com/fwlink/?linkid=89213).
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](http://go.microsoft.com/fwlink/?linkid=33329) 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](http://go.microsoft.com/fwlink/?linkid=169557).
### 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 [October bulletin summary](http://technet.microsoft.com/security/bulletin/ms12-oct). For more information, see [Microsoft Exploitability Index](http://technet.microsoft.com/security/cc998259).
Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Works Heap Vulnerability - CVE-2012-2550
Aggregate Severity Rating
Microsoft Works 9
Remote Code Execution
Works Heap Vulnerability - CVE-2012-2550
A remote code execution vulnerability exists in the way that affected versions of Microsoft Works parse specially crafted Word files. 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. 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.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see [CVE-2012-2550](http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2012-2550).
#### Mitigating Factors for Works Heap Vulnerability - CVE-2012-2550
Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:
- The vulnerability cannot be exploited automatically through email. For an attack to be successful, a user must open an attachment that is sent in an email message.
- An attacker who successfully exploited this vulnerability 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.
#### Workarounds for Works Heap Vulnerability - CVE-2012-2550
Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:
- Do not open Word files that you receive from untrusted sources or that you receive unexpectedly from trusted sources. This vulnerability could be exploited when a user opens a specially crafted file.
#### FAQ for Works Heap Vulnerability - CVE-2012-2550
**What is the scope of the vulnerability?**
This is a remote code execution vulnerability.
**What causes the vulnerability?**
The vulnerability is caused when Microsoft Works parses specially crafted Word (.doc) files, potentially causing system memory corruption that could allow an attacker to execute arbitrary code.
**What might an attacker use the vulnerability to do?**
An attacker who successfully exploited this vulnerability could run arbitrary code as the current user. If the current user is logged on with administrative user rights, an attacker could take complete control of the 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.
**How could an attacker exploit the vulnerability?**
This vulnerability requires that a user open specially crafted Word files with an affected version of Microsoft Works.
In a web-based attack scenario, an attacker could host a website that contains a Works file that is used to attempt to exploit this vulnerability. In addition, compromised websites and websites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. In all cases, an attacker would have no way to force users to visit a specially crafted website. Instead, an attacker would have to convince them to visit the website, typically by getting them to click a link that takes them to the attacker's site, and then convince them to open the specially crafted Works file.
**What systems are primarily at risk from the vulnerability?**
Workstations and terminal servers that have affected versions of Microsoft Works installed are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.
**What does the update do?**
The update addresses the vulnerability by modifying the way that Microsoft Works parses specially crafted Word (.doc) files.
**When this security bulletin was issued, had this vulnerability been publicly disclosed?**
No. Microsoft received information about this vulnerability through coordinated vulnerability disclosure.
**When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being** **exploited?**
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers.
### 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](http://go.microsoft.com/fwlink/?linkid=69903). The [Microsoft TechNet Security website](http://go.microsoft.com/fwlink/?linkid=21132) provides additional information about security in Microsoft products.
Security updates are available from [Microsoft Update](http://go.microsoft.com/fwlink/?linkid=40747) and [Windows Update](http://go.microsoft.com/fwlink/?linkid=21130). Security updates are also available from the [Microsoft Download Center](http://go.microsoft.com/fwlink/?linkid=21129). You can find them most easily by doing a keyword search for "security update."
For customers of Microsoft Office for Mac, Microsoft AutoUpdate for Mac can help keep your Microsoft software up to date. For more information about using Microsoft AutoUpdate for Mac, see [Check for software updates automatically](http://mac2.microsoft.com/help/office/14/en-us/word/item/ffe35357-8f25-4df8-a0a3-c258526c64ea).
Finally, security updates can be downloaded from the [Microsoft Update Catalog](http://go.microsoft.com/fwlink/?linkid=96155). 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, "MS12-001"), you can add all 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](http://go.microsoft.com/fwlink/?linkid=97900).
**Detection and Deployment Guidance**
Microsoft provides detection and deployment guidance for security updates. This guidance contains recommendations and information that can help IT professionals understand how to use various tools for detection and deployment of security updates. For more information, see [Microsoft Knowledge Base Article 961747](http://support.microsoft.com/kb/961747).
**Microsoft Baseline Security Analyzer**
Microsoft Baseline Security Analyzer (MBSA) lets administrators scan local and remote systems for missing security updates as well as common security misconfigurations. For more information, see [Microsoft Baseline Security Analyzer](http://go.microsoft.com/fwlink/?linkid=20567).
The following table provides the MBSA detection summary for this security update.
| Software | MBSA |
| Microsoft Works 9 | Yes |
**Note** For customers using legacy software not supported by the latest release of MBSA, Microsoft Update, and Windows Server Update Services, please see [Microsoft Baseline Security Analyzer](http://go.microsoft.com/fwlink/?linkid=20567) and reference the Legacy Product Support section on how to create comprehensive security update detection with legacy tools.
**Windows Server Update Services**
Windows Server Update Services (WSUS) enables information technology administrators to deploy the latest Microsoft product updates to computers that are running the Windows operating system. For more information about how to deploy security updates using Windows Server Update Services, see the TechNet article, [Windows Server Update Services](http://technet.microsoft.com/wsus/default.aspx).
**Systems Management Server**
The following table provides the SMS detection and deployment summary for this security update.
| Software | SMS 2003 with ITMU | System Center Configuration Manager |
| Microsoft Works 9 | Yes | Yes |
**Note** Microsoft discontinued support for SMS 2.0 on April 12, 2011. For SMS 2003, Microsoft also discontinued support for the Security Update Inventory Tool (SUIT) on April 12, 2011. Customers are encouraged to upgrade to [System Center Configuration Manager](http://technet.microsoft.com/systemcenter/bb980621). For customers remaining on SMS 2003 Service Pack 3, the [Inventory Tool for Microsoft Updates](http://technet.microsoft.com/sms/bb676783.aspx) (ITMU) is also an option.
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](http://update.microsoft.com/microsoftupdate) and that are supported by [Windows Server Update Services](http://go.microsoft.com/fwlink/?linkid=50120). For more information about the SMS 2003 ITMU, see [SMS 2003 Inventory Tool for Microsoft Updates](http://technet.microsoft.com/sms/bb676783.aspx). For more information about SMS scanning tools, see [SMS 2003 Software Update Scanning Tools](http://technet.microsoft.com/sms/bb676786.aspx). See also [Downloads for Systems Management Server 2003](http://technet.microsoft.com/sms/bb676766.aspx).
System Center Configuration Manager uses WSUS 3.0 for detection of updates. For more information, see [System Center](http://technet.microsoft.com/systemcenter/bb980621).
For more detailed information, see [Microsoft Knowledge Base Article 910723](http://support.microsoft.com/kb/910723): Summary list of monthly detection and deployment guidance articles.
**Note** If you have used an Administrative Installation Point (AIP) for deploying 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 2003, see [Creating an Administrative Installation Point](http://office.microsoft.com/en-us/ork2003/ha011401931033.aspx). For more information on how to change the source for a client computer from an updated administrative installation point to an Office 2003 original baseline source or Service Pack 3 (SP3), see [Microsoft Knowledge Base Article 902349](http://support.microsoft.com/kb/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](http://office.microsoft.com/en-us/ork2003/ha011402381033.aspx?pid=ch011480761033).
- For creating a network installation point for supported versions of Microsoft Office, see [Create a network installation point for Microsoft Office](http://technet.microsoft.com/library/cc179063.aspx).
**Note** If you plan to manage security updates centrally, use Windows Server Update Services. For more information about how to deploy security updates for Microsoft Office, see the [Windows Server Update Services website](http://technet.microsoft.com/wsus/default.aspx).
**Update Compatibility Evaluator and Application Compatibility Toolkit**
Updates often write to the same files and registry settings required for your applications to run. This can trigger incompatibilities and increase the time it takes to deploy security updates. You can streamline testing and validating Windows updates against installed applications with the [Update Compatibility Evaluator](http://technet.microsoft.com/library/cc749197) components included with [Application Compatibility Toolkit](https://www.microsoft.com/download/details.aspx?familyid=24da89e9-b581-47b0-b45e-492dd6da2971).
The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.
Security Update Deployment
For information about the specific security update for your affected software, click the appropriate link:
#### Microsoft Works 9
The following table contains the security update information for this software. You can find additional information in the subsection, **Deployment Information**, in this section.
Inclusion in Future Service Packs
The update for this issue will be included in a future service pack or update rollup
Installing without user intervention
Installing without restarting
Update log file
For detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance.
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.
#### Deployment Information
**Installing the Update**
You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the **Office Administrative Installation Point** information in the **Detection and deployment Tools and Guidance** subsection.
This security update requires that Windows Installer 3.1 or later version be installed on the system.
To install the 3.1 or later version of Windows Installer, see one of the following Microsoft websites:
- [Windows Installer 4.5 Redistributable for Windows Server 2008, Windows Vista, Windows Server 2003, and Windows XP](https://www.microsoft.com/download/details.aspx?familyid=5a58b56f-60b6-4412-95b9-54d056d6f9f4)
- [Windows Installer 3.1 Redistributable for Windows Server 2003, Windows XP, and Microsoft Windows 2000](https://www.microsoft.com/download/details.aspx?familyid=889482fc-5f56-4a38-b838-de776fd4138c)
For more information about the terminology that appears in this bulletin, such as hotfix, see [Microsoft Knowledge Base Article 824684](http://support.microsoft.com/kb/824684).
This security update supports the following setup switches.
Supported Security Update Installation Switches
Displays the command-line options.
/quiet or /q[n|b|r|f]
Quiet mode, no user interaction or
/q[n|b|r|f] sets user interface level:
n - No user interface
b - Basic user interface
r - Reduced user interface
f - Full user interface (default)
Unattended mode - progress bar only.
Do not restart after the installation is complete.
Enables logging. Options:
i - Status messages
w - Nonfatal warnings
e - All error messages
a - Start up of actions
r - Action-specific records
u - User requests
c - Initial UI parameters
m - Out-of-memory or fatal exit information
o - Out-of-disk-space messages
p - Terminal properties
v - Verbose output
x - Extra debugging information
+ - Append to existing log file
! - Flush each line to the log
* - Log all information, except for v and x options
Equivalent of /l* <LogFile>.
**Note** You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see [Microsoft Knowledge Base Article 262841](http://support.microsoft.com/kb/262841).
**Removing the Update**
To remove this security update, use the **Add or Remove Programs** item in Control Panel.
**Note** When you remove this update, you may be prompted to insert the 2007 Microsoft Office 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](http://support.microsoft.com/kb/903771).
**Verifying that the Update Has Been Applied**
- **Microsoft Baseline Security Analyzer**
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, **Detection and Deployment Tools and Guidance**, earlier in this bulletin for more information.
- **File Version Verification**
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
1. Click **Start** and then enter an update file name in the **Start Search** box.
2. When the file appears under **Programs**, right-click the file name and click **Properties**.
3. On the **General** tab, compare the file size with the file information tables provided in the bulletin KB article.
**Note** Depending on the edition of the operating system, or the programs that are installed on your system, some files that are listed in the file information table may not be installed.
4. You can also click the **Details** tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
**Note** Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
5. Finally, you can also click the **Previous Versions** tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
### Other Information
#### 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 go to the active protections websites provided by program partners, listed in [Microsoft Active Protections Program (MAPP) Partners](http://go.microsoft.com/fwlink/?linkid=215201).
**How to obtain help and support for this security update**
- Help installing updates: [Support for Microsoft Update](http://support.microsoft.com/ph/6527)
- Security solutions for IT professionals: [TechNet Security Troubleshooting and Support](http://technet.microsoft.com/security/bb980617.aspx)
- Help protect your computer that is running Windows from viruses and malware: [Virus Solution and Security Center](http://support.microsoft.com/contactus/cu_sc_virsec_master)
- Local support according to your country: [International Support](http://support.microsoft.com/common/international.aspx)
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.
- V1.0 (October 9, 2012): Bulletin published.
*Built at 2014-04-18T13:49:36Z-07:00*