Microsoft Word Mac 2011 Updates
Aug 27, 2018 So if you want Office 2011 updates, and you are running OSX 10.5-10.9, you NOW need to manually search for the updates at the 'Official Microsoft Download Center'. For instance, here is the direct link to MS Office for Mac 2011 - 14.7.2 Update, released on 6 March 2017. Oct 11, 2019 Want to update to macOS Catalina but can't justify losing access to all the outdated 32-bit apps I rely on (looking at you Microsoft Word for Mac 2011). Oct 11, 2017 Microsoft has officially ended support for Office for Mac 2011 as scheduled, nearly seven years after the software suite was first released. 2011 versions of Word, Excel, Outlook, and PowerPoint. Jul 22, 2019 Here are some articles for your reference: Start page numbering later in your document in Word for Mac; Add or remove page numbers in Word for Mac; Insert, delete, or change a section break. Hope the information was helpful. If you have any updates, feel.
- Microsoft Word Mac 2011 Updates Free
- Update Microsoft Word 2011
- Microsoft Office Mac
- Microsoft Word 2011 Update
- Microsoft Word 2011 Update For Mac
- Word For Mac 2011
AutoUpdate 3.0.5 was installed with the last Office update a few days ago. Microsoft has backed off from the mess it made with a new version of AutoUpdate you can download now. The problem only happens if you're using both the Office 2016 preview Microsoft has posted as well as Office 2011.
Once you installed the previous version of AutoUpdate, you'd find that it would locate but would be unable to install an update to Office 2011. What's worse, the AutoUpdate program would grab lots of memory and generally make a mess of things. People were running into this problem:
To get past it, the easiest thing to do is to to run AutoUpdate again. It'll find the updated version of itself and install it. To do so, just select the 'Check for Updates' option in the Help menu of any open Microsoft application.
If that doesn't work, or if you don't trust AutoUpdate to do the right thing, you can download the latest updater from Microsoft's web site and install it yourself. That'll download to your Downloads folder as a .pkg file.
How to run the AutoUpdate installer
- Double-click on 'Microsoft AutoUpdate 3.0.6.pkg' to launch the installer.
- Click Continue.
- Click Continue again to install it to your Mac's hard drive.
- Click Install.
- Enter your administrator password and click Install Software.
- After it's done click the Close button.
That's it.
We may earn a commission for purchases using our links. Learn more.
For all your USB-C needsThe HybridDrive is a USB-C dock with an SSD built in
You need more ports, right? And you probably need more storage, right? What you really need is the HybridDrive.
-->Security Bulletin
Vulnerability in Microsoft Office Could Allow Remote Code Execution (2590602)
Published: December 13, 2011 Updated: February 22, 2012
Version: 1.2
General Information
Executive Summary
This security update resolves a privately reported vulnerability in Microsoft Office. The vulnerability could allow remote code execution if a user opens a specially crafted Word file. An attacker who successfully exploited this vulnerability could gain the same user rights as the logged-on 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.
Microsoft Word Mac 2011 Updates Free
This security update is rated Important for all supported editions of Microsoft Office 2007, Microsoft Office 2010, and Microsoft Office for Mac 2011. For more information, see the subsection, Affected and Non-Affected Software, in this section.
The security update addresses the vulnerability by correcting the way that Microsoft Word parses specially crafted Word 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 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, visit Microsoft Support Lifecycle.
Affected Software
| Microsoft Office Suite and Other Software | Maximum Security Impact | Aggregate Severity Rating | Bulletins Replaced by this Update | |
|---|---|---|---|---|
| Microsoft Office Suites and Components | ||||
| [Microsoft Office 2007 Service Pack 2 and Microsoft Office 2007 Service Pack 3](https://www.microsoft.com/download/details.aspx?familyid=e924cd85-5764-4056-bd32-b0e57dc25146) (KB2596785) | Remote Code Execution | Important | None | |
| [Microsoft Office 2010 and Microsoft Office 2010 Service Pack 1 (32-bit editions)](https://www.microsoft.com/download/details.aspx?familyid=e47c0694-a9a5-4dd7-bfba-e470d9855c28) (KB2589320) | Remote Code Execution | Important | None | |
| [Microsoft Office 2010 and Microsoft Office 2010 Service Pack 1 (64-bit editions)](https://www.microsoft.com/download/details.aspx?familyid=6c2d5273-eef9-4ff6-be6f-8d86f417f004) (KB2589320) | Remote Code Execution | Important | None | |
| Microsoft Office for Mac | ||||
| [Microsoft Office for Mac 2011](https://www.microsoft.com/download/details.aspx?familyid=3c8017d6-232c-42a6-a133-96efe3ad3385) (KB2644347) | Remote Code Execution | Important | [MS11-072](http://go.microsoft.com/fwlink/?linkid=225047) | |
| Office and Other Software |
|---|
| Microsoft SharePoint Server 2010 and Microsoft SharePoint Server 2010 Service Pack 1 |
| Microsoft Office Web Application Companions (WAC) |
| Microsoft Office 2003 Service Pack 3 |
| Microsoft Office 2004 for Mac |
| Microsoft Office 2008 for Mac |
| Open XML File Format Converter for Mac |
| Microsoft Visio 2010 and Microsoft Visio 2010 Service Pack 1 (32-bit editions) |
| Microsoft Visio 2010 and Microsoft Visio 2010 Service Pack 1 (64-bit editions) |
| Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 2 |
| Microsoft Office Compatibility Pack Service Pack 3 |
| Microsoft Office Word Viewer |
| Microsoft Visio Viewer 2010 and Microsoft Visio Viewer 2010 Service Pack 1 |
| Microsoft Works 9 |
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.
Why is this update only rated Important for affected versions of Office?
Microsoft Office XP and later versions have a built-in feature that prompts a user to Open, Save, or Cancel before opening a document. This mitigating factor reduces the vulnerability from Critical to Important because the vulnerability requires more than a single user action to complete the exploit.
The attack vector for the vulnerability is through Microsoft Word. Why is this a Microsoft Office update?
Although the attack vector for CVE-2011-1983 is only through affected versions of Microsoft Word, the vulnerable code is contained in a shared component of Microsoft Office. Other Microsoft Office software, including some supported releases of Microsoft Visio (see KB2553374 (x86) and KB2553374 (x64)), Microsoft Visio Viewer (see KB2553353 (x86) and KB2553353 (x64)), Microsoft Office Web Application Companions (WAC) (see KB2553153), and Microsoft SharePoint Server 2010 (see KB2553132), contain the vulnerable shared component of Microsoft Office, but because they do not access the vulnerable code, they are not affected by this vulnerability. However, since the vulnerable code is present, this update will be offered.
I have Microsoft Office software installed, why might I not be offered this update?
The update will only be offered to systems running Microsoft Office software that contains the vulnerable shared component of Microsoft Office.
Note that the attack vector for CVE-2011-1983 is only through affected versions of Microsoft Word. Other Microsoft Office software may be offered this update because the vulnerable shared component of Microsoft Office is present, but because the vulnerable code is not accessed, they are not affected by the vulnerability.
Does the offer to update a non-vulnerable version of Microsoft Officesoftwareconstitute an issue in the Microsoft update mechanism?
No, the update mechanism is functioning correctly in that it detects a lower version of the files on the system than in the update package 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, visit the Microsoft Support Lifecycle Web site.
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, visit the Microsoft Worldwide Information Web site, 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 December bulletin summary. For more information, see Microsoft Exploitability Index.
| Affected Software | Word Use After Free Vulnerability - CVE-2011-1983 | Aggregate Severity Rating |
|---|---|---|
| Microsoft Office Suites and Components | ||
| Microsoft Office 2007 Service Pack 2 and Microsoft Office 2007 Service Pack 3 | **Important** Remote Code Execution | **Important** |
| Microsoft Office 2010 and Microsoft Office 2010 Service Pack 1 (32-bit editions) | **Important** Remote Code Execution | **Important** |
| Microsoft Office 2010 and Microsoft Office 2010 Service Pack 1 (64-bit editions) | **Important** Remote Code Execution | **Important** |
| Microsoft Office for Mac | ||
| Microsoft Office for Mac 2011 | **Important** Remote Code Execution | **Important** |
Word Use After Free Vulnerability - CVE-2011-1983
A remote code execution vulnerability exists in the way that Microsoft Word handles 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.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2011-1983.
Mitigating Factors for Word Use After Free Vulnerability - CVE-2011-1983
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:
- In a Web-based attack scenario, an attacker could host a Web site that contains a Word file that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker’s Web site, and then convince them to open the specially crafted Word file.
- The vulnerability cannot be exploited automatically through e-mail. For an attack to be successful, a user must open an attachment that is sent in an e-mail message.
- An attacker who successfully exploited this vulnerability could gain the same user rights as the logged-on 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 Word Use After Free Vulnerability - CVE-2011-1983
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 Office files that you receive from untrusted sources or that you receive unexpectedly from trusted sources
Do not open Office 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 Word Use After Free Vulnerability - CVE-2011-1983
What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could take complete control of an affected system remotely. An attacker could then install programs or view, change, or delete data; or create new accounts with full user rights.
What causes the vulnerability?
The vulnerability is caused when Microsoft Word improperly handles objects in memory.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could run arbitrary code as the logged-on user. If a 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?
Exploitation of this vulnerability requires that a user open a specially crafted Word file with an affected version of Microsoft Word.
In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially crafted Word file to the user and by convincing the user to open the file.
In a Web-based attack scenario, an attacker would have to host a Web site that contains a Word file that is used to attempt to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit a specially crafted Web site. Instead, an attacker would have to convince them to visit the Web site, 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 Word file.
What systems are primarily at risk from the vulnerability?
Systems where Microsoft Word is used, such as workstations, 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 correcting the way that Microsoft Word parses specially crafted Word 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 when this security bulletin was originally issued.
Update Information
Detection and Deployment Tools and Guidance
Security Central
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 and Windows 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.'
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.
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 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.
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.
The following table provides the MBSA detection summary for this security update.
| Software | MBSA |
|---|---|
| Microsoft Office 2007 Service Pack 2 and Microsoft Office 2007 Service Pack 3 | Yes |
| Microsoft Office 2010 and Microsoft Office 2010 Service Pack 1 (32-bit editions) | Yes |
| Microsoft Office 2010 and Microsoft Office 2010 Service Pack 1 (64-bit editions) | Yes |
| Microsoft Office for Mac 2011 | No |
Note For customers using legacy software not supported by the latest release of MBSA, 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
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.
Systems Management Server
The following table provides the SMS detection and deployment summary for this security update.
| Software | SMS 2003 with ITMU | Configuration Manager 2007 |
|---|---|---|
| Microsoft Office 2007 Service Pack 2 and Microsoft Office 2007 Service Pack 3 | Yes | Yes |
| Microsoft Office 2010 and Microsoft Office 2010 Service Pack 1 (32-bit editions) | Yes | Yes |
| Microsoft Office 2010 and Microsoft Office 2010 Service Pack 1 (64-bit editions) | Yes | Yes |
| Microsoft Office for Mac 2011 | No | No |
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 2007. For customers remaining on SMS 2003 Service Pack 3, the Inventory Tool for Microsoft Updates (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 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. For more information about SMS scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003.
System Center Configuration Manager 2007 uses WSUS 3.0 for detection of updates. For more information about Configuration Manager 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 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 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, 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. 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.
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 creating a network installation point for supported versions of Microsoft Office, see Create a network installation point for Microsoft Office.
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, visit the Windows Server Update Services Web site.
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 components included with Application Compatibility Toolkit.
The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Microsoft Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.
Security Update Deployment
Affected Software
For information about the specific security update for your affected software, click the appropriate link:
Microsoft Office 2007 (all editions)
Reference Table
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 |
| Deployment | |
| Installing without user intervention | msptls2007-kb2596785-fullfile-x86-glb.exe /passive |
| Installing without restarting | msptls2007-kb2596785-fullfile-x86-glb.exe /norestart |
| Update log file | Not applicable |
| Further information | For detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance. |
| Restart Requirement | |
| Restart required? | 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. |
| HotPatching | Not applicable |
| Removal Information | Use Add or Remove Programs tool in Control Panel. |
| File Information | See Microsoft Knowledge Base Article 2596785 |
| Registry Key Verification | Not applicable |
Supported Security Update Installation Switches
| Switch | Description |
|---|---|
| /? or /help | Displays usage dialog. |
| /passive | Specifies passive mode. Requires no user interaction; users see basic progress dialogs but cannot cancel. |
| /quiet | Specifies quiet mode, or suppresses prompts, when files are being extracted. |
| /norestart | Suppresses restarting the system if the update requires a restart. |
| /forcerestart | Automatically restarts the system after applying the update, regardless of whether the update requires the restart. |
| /extract | Extracts the files without installing them. You are prompted for a target folder. |
| /extract:<path> | Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file. |
| /lang:<LCID> | Forces the use of a specific language, when the update package supports that language. |
| /log:<log file> | Enables logging, by both Vnox and Installer, during the update installation. |
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.
Removing the Update
To remove this security update, use the Add or Remove Programs tool in Control Panel.
Update Microsoft Word 2011
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 tool in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 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.
- Click Start and then enter an update file name in the Start Search box.
- When the file appears under Programs, right-click the file name and click Properties.
- 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 of the files that are listed in the file information table may not be installed. - 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. - 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.
Microsoft Office 2010 (all editions)
Reference Table
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 |
| Deployment | |
| Installing without user intervention | For Microsoft Office 2010 (32-bit editions): msptls2010-kb2589320-fullfile-x86-glb.exe /passive |
| For Microsoft Office 2010 (64-bit editions): msptls2010-kb2589320-fullfile-x64-glb /passive | |
| Installing without restarting | For Microsoft Office 2010 (32-bit editions): msptls2010-kb2589320-fullfile-x86-glb.exe /norestart |
| For Microsoft Office 2010 (64-bit editions): msptls2010-kb2589320-fullfile-x64-glb /norestart | |
| Update log file | Not applicable |
| Further information | For detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance. |
| RestartRequirement | |
| Restart required? | 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. |
| HotPatching | Not applicable |
| Removal Information | Use Add or Remove Programs tool in Control Panel. |
| File Information | See Microsoft Knowledge Base Article 2589320 |
| Registry Key Verification | Not applicable |
Supported Security Update Installation Switches
| Switch | Description |
|---|---|
| /? or /help | Displays usage dialog. |
| /passive | Specifies passive mode. Requires no user interaction; users see basic progress dialogs but cannot cancel. |
| /quiet | Specifies quiet mode, or suppresses prompts, when files are being extracted. |
| /norestart | Suppresses restarting the system if the update requires a restart. |
| /forcerestart | Automatically restarts the system after applying the update, regardless of whether the update requires the restart. |
| /extract | Extracts the files without installing them. You are prompted for a target folder. |
| /extract:<path> | Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file. |
| /lang:<LCID> | Forces the use of a specific language, when the update package supports that language. |
| /log:<log file> | Enables logging, by both Vnox and Installer, during the update installation. |
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.
Removing the Update
To remove this security update, use the Add or Remove Programs tool 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 tool in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 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.
- Click Start and then enter an update file name in the Start Search box.
- When the file appears under Programs, right-click the file name and click Properties.
- 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 of the files that are listed in the file information table may not be installed. - 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. - 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.
Office for Mac 2011
Deployment Information
Prerequisites
- Mac OS X version 10.5.8 or later on an Intel processor
- Mac OS X user accounts must have administrator privileges to install this security update
Installing the Update
Download and install the appropriate language version of the Microsoft Office for Mac 2011 14.1.4 Update from the Microsoft Download Center.
Microsoft himalaya for mac. iMac (Retina 5K, 27-inch, Late 2014 - 2015). iMac (Retina 4K, 21.5-inch, Late 2015). Mac Pro (2019). iMac (Retina 5K, 27-inch, 2017). Mac Pro (Late 2013).
Microsoft Office Mac
- Quit any applications that are running, including virus-protection applications and all Microsoft Office applications, because they might interfere with installation.
- Open the Microsoft Office for Mac 2011 14.1.4 Update volume on your desktop. This step might have been performed for you.
- To start the update process, in the Microsoft Office for Mac 2011 14.1.4 Update volume window, double-click the Microsoft Office for Mac 2011 14.1.4 Update application, and follow the instructions on the screen.
- When the installation finishes successfully, you can remove the update installer from your hard disk. To verify that the installation finished successfully, see the following 'Verifying Update Installation' heading. To remove the update installer, first drag the Microsoft Office for Mac 2011 14.1.4 Update volume to the Trash, and then drag the file that you downloaded to the Trash.
Verifying Update Installation
To verify that a security update is installed on an affected system, follow these steps:
- In the Finder, navigate to the Application Folder (Microsoft Office 2011).
- Select Word, Excel, PowerPoint or Outlook and launch the application.
- On the Application menu, click AboutApplication_Name (where Application_Name is Word, Excel, PowerPoint or Outlook).
If the Latest Installed Update Version number is 14.1.4, the update has been successfully installed.
Restart Requirement
This update does not require you to restart your computer.
Removing the Update
This security update cannot be uninstalled.
Additional Information
Microsoft Word 2011 Update
If you have technical questions or problems downloading or using this update, visit Microsoft for Mac Support to learn about the support options that are available to you.
Other Information
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
- Nikita Tarakanov (CISS Research Team) and Alexey Sintsov (Digital Security Research Group), working with TippingPoint'sZero Day Initiative, for reporting the Word Use After Free Vulnerability (CVE-2011-1983)
Microsoft Active Protections Program (MAPP)
Microsoft Word 2011 Update For Mac
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.
Support
Word For Mac 2011
- Customers in the U.S. and Canada can receive technical support from Security Support or 1-866-PCSAFETY (1-866-727-2338). 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 the International Support Web site.
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 13, 2011): Bulletin published.
- V1.1 (December 16, 2011): Expanded the list of non-affected software and revised the Update FAQ to help clarify that this update may be offered to non-affected software when the vulnerable shared component of Microsoft Office is present.
- V1.2 (February 22, 2012): Revised the bulletin to identify the update package KB numbers for the following non-affected software that this update applies to: Microsoft Visio (KB2553374), Microsoft Visio Viewer (KB2553353), Microsoft Office Web Application Companions (WAC) (KB2553153), and Microsoft SharePoint Server 2010 (KB2553132). See the update FAQ for details.
Built at 2014-04-18T13:49:36Z-07:00