Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Microsoft Security Bulletin MS11-008 - Important

Vulnerabilities in Microsoft Visio Could Allow Remote Code Execution (2451879)

Published: February 08, 2011

Version: 1.0

General Information

Executive Summary

This security update resolves two privately reported vulnerabilities in Microsoft Visio. The vulnerabilities could allow remote code execution if a user opens a specially crafted Visio file. An attacker who successfully exploited either of these vulnerabilities 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.

This security update is rated Important for Microsoft Visio 2002 Service Pack 2, Microsoft Visio 2003 Service Pack 3, and Microsoft Visio 2007 Service Pack 2. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses the vulnerabilities by correcting the way that Microsoft Visio handles corrupted structures and objects in memory when parsing specially crafted Visio files. 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. Microsoft recommends that customers apply the update at the earliest opportunity.

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 and Other Productivity SoftwareMaximum Security ImpactAggregate Severity RatingBulletins Replaced by this Update
Microsoft Visio 2002 Service Pack 2
(KB2434711)
Remote Code ExecutionImportant MS10-028
Microsoft Visio 2003 Service Pack 3
(KB2434733)
Remote Code ExecutionImportant MS10-036
Microsoft Visio 2007 Service Pack 2
(KB2434737)
Remote Code ExecutionImportant MS10-036

Non-Affected Software

Office and Other Software
Microsoft Visio 2010 (32-bit editions)
Microsoft Visio 2010 (64-bit editions)
Microsoft Visio 2007 Viewer
Microsoft Visio 2010 Viewer

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 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. Instead of having to install several updates that are almost the same, customers need to install this update only.

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 Lifecycle Supported Service Packs.

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

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 February bulletin summary. For more information, see Microsoft Exploitability Index.

Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected SoftwareVisio Object Memory Corruption Vulnerability - CVE-2011-0092Visio Data Type Memory Corruption Vulnerability - CVE-2011-0093Aggregate Severity Rating
Microsoft Visio 2002 Service Pack 2 Important 
Remote Code Execution
Important 
Remote Code Execution
Important
Microsoft Visio 2003 Service Pack 3 Important 
Remote Code Execution
Important 
Remote Code Execution
Important
Microsoft Visio 2007 Service Pack 2 Important 
Remote Code Execution
Important 
Remote Code Execution
Important

A remote code execution vulnerability exists in the way that Microsoft Visio validates objects in memory when parsing specially crafted Visio 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 affected 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-2011-0092.

Mitigating Factors for Visio Object Memory Corruption Vulnerability - CVE-2011-0092

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:

  • 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.
  • 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.
  • In a Web-based attack scenario, an attacker would have to host a Web site that contains a specially crafted Visio 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 these Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link that takes users to the attacker's Web site, and then convince them to open a specially crafted Visio file.

Workarounds for Visio Object Memory Corruption Vulnerability - CVE-2011-0092

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:

  • Restrict Access to ORMELEMS.DLL

    Run the following commands from a command prompt as an administrator:

    For 32-bit editions of Windows XP and Windows Server 2003:

    cacls "%ProgramFiles%\Microsoft Office\<office version>\ormelems.dll" /E /P everyone:N

    Note For <office version>, enter the version of the appropriate Microsoft Office component in your system, such as "Office10" for Microsoft Visio 2002, "Office11" for Microsoft Visio 2003, and "Office12" for Microsoft Visio 2007. To verify the version, open this Microsoft Office component and click Help.

    For 64-bit editions of Windows XP and Windows Server 2003:

    cacls "%ProgramFiles(86)%\Microsoft Office\<office version>\ormelems.dll" /E /P everyone:N

    Note For <office version>, enter the version of the appropriate Microsoft Office component in your system, such as "Office10" for Microsoft Visio 2002, "Office11" for Microsoft Visio 2003, and "Office12" for Microsoft Visio 2007. To verify the version, open this Microsoft Office component and click Help.

    For 32-bit editions of Windows Vista, Windows Server 2008, and Windows 7:

    cacls "%ProgramFiles%\Microsoft Office\<office version>\ormelems.dll" /E /P everyone:N

    Note For <office version>, enter the version of the appropriate Microsoft Office component in your system, such as "Office10" for Microsoft Visio 2002, "Office11" for Microsoft Visio 2003, and "Office12" for Microsoft Visio 2007. To verify the version, open this Microsoft Office component and click Help.

    For 64-bit editions of Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2:

    cacls "%ProgramFiles(86)%\Microsoft Office\<office version>\ormelems.dll" /E /P everyone:N

    Note For <office version>, enter the version of the appropriate Microsoft Office component in your system, such as "Office10" for Microsoft Visio 2002, "Office11" for Microsoft Visio 2003, and "Office12" for Microsoft Visio 2007. To verify the version, open this Microsoft Office component and click Help.

    Impact of workaround. Users will not be able to use the Database Modeling feature in Visio.

    How to undo the workaround:

    Run the following command from a command prompt as an administrator:

    For 32-bit editions of Windows XP and Windows Server 2003:

    cacls "%ProgramFiles%\Microsoft Office\<office version>\ormelems.dll" /E /R everyone

    Note For <office version>, enter the version of the appropriate Microsoft Office component in your system, such as "Office10" for Microsoft Visio 2002, "Office11" for Microsoft Visio 2003, and "Office12" for Microsoft Visio 2007. To verify the version, open this Microsoft Office component and click Help.

    For 64-bit editions of Windows XP and Windows Server 2003:

    cacls "%ProgramFiles(86)%\Microsoft Office\<office version>\ormelems.dll" /E /R everyone

    Note For <office version>, enter the version of the appropriate Microsoft Office component in your system, such as "Office10" for Microsoft Visio 2002, "Office11" for Microsoft Visio 2003, and "Office12" for Microsoft Visio 2007. To verify the version, open this Microsoft Office component and click Help.

    For 32-bit editions of Windows Vista, Windows Server 2008, and Windows 7:

    takeown /f "%ProgramFiles%\Microsoft Office\<office version>\ormelems.dll"
    cacls "%ProgramFiles%\Microsoft Office\<office version>\ormelems.dll" /E /R everyone

    Note For <office version>, enter the version of the appropriate Microsoft Office component in your system, such as "Office10" for Microsoft Visio 2002, "Office11" for Microsoft Visio 2003, and "Office12" for Microsoft Visio 2007. To verify the version, open this Microsoft Office component and click Help.

    For 64-bit editions of Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2:

    takeown /f "%ProgramFiles(86)%\Microsoft Office\<office version>\ormelems.dll"
    cacls "%ProgramFiles(86)%\Microsoft Office\<office version>\ormelems.dll" /E /R everyone

    Note For <office version>, enter the version of the appropriate Microsoft Office component in your system, such as "Office10" for Microsoft Visio 2002, "Office11" for Microsoft Visio 2003, and "Office12" for Microsoft Visio 2007. To verify the version, open this Microsoft Office component and click Help.

  • Disable Add-ins in Microsoft Visio 2007

    Open Visio 2007 and follow the steps below:

    1. Click Tools.
    2. Click Trust Center.
    3. Click Add-ins.
    4. Ensure the Disable all Application Add-ins check box is selected.
    5. Click OK to apply Settings.

    Impact of workaround. Functionality that relies on Visio add-ins will not work.

    How to undo the workaround.

    Open Visio 2007 and follow the steps below:

    1. Click Tools.
    2. Click Trust Center.
    3. Click Add-ins.
    4. Ensure the Disable all Application Add-ins check box is not selected.
    5. Click OK to apply Settings.
  • Do not open Office files that you receive from untrusted sources or that you receive unexpectedly from trusted sources

    Do not open Visio 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 Visio Object Memory Corruption Vulnerability - CVE-2011-0092

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. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

What causes the vulnerability? 
Microsoft Visio does not properly validate objects in memory when parsing specially crafted Visio files.

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? 
This vulnerability requires that a user open a specially crafted Visio file with an affected version of Microsoft Visio.

In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially crafted Visio 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 specially crafted Visio 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 these Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link that takes them to the attacker's Web site, and then convinced them to open a specially crafted Visio file.

What systems are primarily at risk from the vulnerability? 
Systems where Microsoft Visio is used, including workstations and terminal servers, 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? 
This update addresses the vulnerability by correcting the way that Microsoft Visio validates objects in memory when parsing specially crafted Visio 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.

A remote code execution vulnerability exists in the way that Microsoft Visio parses certain structures when handling specially crafted Visio 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 affected 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-2011-0093.

Mitigating Factors for Visio Data Type Memory Corruption Vulnerability - CVE-2011-0093

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:

  • 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.
  • 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.
  • In a Web-based attack scenario, an attacker would have to host a Web site that contains a specially crafted Visio 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 these Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link that takes users to the attacker's Web site, and then convince them to open a specially crafted Visio file.

Workarounds for Visio Data Type Memory Corruption Vulnerability - CVE-2011-0093

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:

  • Restrict Access to ELEMENTS.DLL

    Run the following commands from a command prompt as an administrator:

    For 32-bit editions of Windows XP and Windows Server 2003:

    cacls "%ProgramFiles%\Microsoft Office\<office version>\elements.dll" /E /P everyone:N

    Note For <office version>, enter the version of the appropriate Microsoft Office component in your system, such as "Office10" for Microsoft Visio 2002, "Office11" for Microsoft Visio 2003, and "Office12" for Microsoft Visio 2007. To verify the version, open this Microsoft Office component and click Help.

    For 64-bit editions of Windows XP and Windows Server 2003:

    cacls "%ProgramFiles(86)%\Microsoft Office\<office version>\elements.dll" /E /P everyone:N

    Note For <office version>, enter the version of the appropriate Microsoft Office component in your system, such as "Office10" for Microsoft Visio 2002, "Office11" for Microsoft Visio 2003, and "Office12" for Microsoft Visio 2007. To verify the version, open this Microsoft Office component and click Help.

    For 32-bit editions of Windows Vista, Windows Server 2008, and Windows 7:

    cacls "%ProgramFiles%\Microsoft Office\<office version>\elements.dll" /E /P everyone:N

    Note For <office version>, enter the version of the appropriate Microsoft Office component in your system, such as "Office10" for Microsoft Visio 2002, "Office11" for Microsoft Visio 2003, and "Office12" for Microsoft Visio 2007. To verify the version, open this Microsoft Office component and click Help.

    For 64-bit editions of Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2:

    cacls "%ProgramFiles(86)%\Microsoft Office\<office version>\elements.dll" /E /P everyone:N

    Note For <office version>, enter the version of the appropriate Microsoft Office component in your system, such as "Office10" for Microsoft Visio 2002, "Office11" for Microsoft Visio 2003, and "Office12" for Microsoft Visio 2007. To verify the version, open this Microsoft Office component and click Help.

    Impact of workaround. Users will not be able to use the Database Modeling feature in Visio.

    How to undo the workaround:

    Run the following command from a command prompt as an administrator:

    For 32-bit editions of Windows XP and Windows Server 2003:

    cacls "%ProgramFiles%\Microsoft Office\<office version>\elements.dll" /E /R everyone

    Note For <office version>, enter the version of the appropriate Microsoft Office component in your system, such as "Office10" for Microsoft Visio 2002, "Office11" for Microsoft Visio 2003, and "Office12" for Microsoft Visio 2007. To verify the version, open this Microsoft Office component and click Help.

    For 64-bit editions of Windows XP and Windows Server 2003:

    cacls "%ProgramFiles(86)%\Microsoft Office\<office version>\elements.dll" /E /R everyone

    Note For <office version>, enter the version of the appropriate Microsoft Office component in your system, such as "Office10" for Microsoft Visio 2002, "Office11" for Microsoft Visio 2003, and "Office12" for Microsoft Visio 2007. To verify the version, open this Microsoft Office component and click Help.

    For 32-bit editions of Windows Vista, Windows Server 2008, and Windows 7:

    Takeown /f "%ProgramFiles%\Microsoft Office\<office version>\elements.dll"
    cacls "%ProgramFiles%\Microsoft Office\<office version>\elements.dll" /E /R everyone

    Note For <office version>, enter the version of the appropriate Microsoft Office component in your system, such as "Office10" for Microsoft Visio 2002, "Office11" for Microsoft Visio 2003, and "Office12" for Microsoft Visio 2007. To verify the version, open this Microsoft Office component and click Help.

    For 64-bit editions of Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2:

    Takeown /f "%ProgramFiles(86)%\Microsoft Office\<office version>\elements.dll"
    cacls "%ProgramFiles(86)%\Microsoft Office\<office version>\elements.dll" /E /R everyone

    Note For <office version>, enter the version of the appropriate Microsoft Office component in your system, such as "Office10" for Microsoft Visio 2002, "Office11" for Microsoft Visio 2003, and "Office12" for Microsoft Visio 2007. To verify the version, open this Microsoft Office component and click Help.

  • Disable Add-ins in Microsoft Visio 2007

    Open Visio 2007 and follow the steps below:

    1. Click Tools.
    2. Click Trust Center.
    3. Click Add-ins.
    4. Ensure the Disable all Application Add-ins check box is selected.
    5. Click OK to apply Settings.

    Impact of workaround. Functionality that relies on Visio add-ins will not work.

    How to undo the workaround.

    Open Visio 2007 and follow the steps below:

    1. Click Tools.
    2. Click Trust Center.
    3. Click Add-ins.
    4. Ensure the Disable all Application Add-ins check box is not selected.
    5. Click OK to apply Settings.
  • Do not open Office files that you receive from untrusted sources or that you receive unexpectedly from trusted sources

    Do not open Visio 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 Visio Data Type Memory Corruption Vulnerability - CVE-2011-0093

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. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

What causes the vulnerability? 
Microsoft Visio does not properly handle corrupted structures when opening specially crafted Visio files.

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? 
This vulnerability requires that a user open a specially crafted Visio file with an affected version of Microsoft Visio.

In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially crafted Visio 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 specially crafted Visio 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 these Web sites. Instead, an attacker would have to convince users 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 a specially crafted Visio file.

What systems are primarily at risk from the vulnerability? 
Systems where Microsoft Visio is used, including workstations and terminal servers, 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? 
This update addresses the vulnerability by correcting the way that Microsoft Visio parses corrupted structures when opening specially crafted Visio 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

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 Visio 2002 Service Pack 2Yes
Microsoft Visio2003 Service Pack 3Yes
Microsoft Visio 2007 Service Pack 2Yes

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.

SoftwareSMS 2.0SMS 2003 with SUITSMS 2003 with ITMUConfiguration Manager 2007
Microsoft Visio 2002 Service Pack 2NoNoYesYes
Microsoft Visio 2003 Service Pack 3NoNoYesYes
Microsoft Visio 2007 Service Pack 2NoNoYesYes

For SMS 2.0 and SMS 2003, 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. 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.

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.

Affected Software

For information about the specific security update for your affected software, click the appropriate link:

Visio 2002 (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 There are no more service packs planned for this software. The update for this issue may be included in a future update rollup.
Deployment
Installing without user interventionvisio2002-KB2434711-fullfile-enu.exe /q:a
Installing without restartingvisio2002-KB2434711-fullfile-enu.exe /r:n
Update log fileNot applicable
Further informationFor detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance. 

For features you can selectively install, see the Office Features for Administrative Installations subsection in this section.
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.
HotPatchingNot applicable
Removal Information This update cannot be uninstalled.
File Information See Microsoft Knowledge Base Article 2434711
Registry Key Verification Not applicable

Office Features

The following table contains the list of feature names (case sensitive) that must be reinstalled for the update. To install all features, you can use REINSTALL=ALL or you can install the following features:

ProductFeature
VISVEA, VISPRO, VISPRORBuilding_Plan_Unitless, CAD_Drawing_Display_Unitless, Database_Design_Unitless, Organization_Charts_Unitless, Software_Design_Unitless,VisioCore
VISSTD, VISSTDRProductFiles
EXCELEXCELNonBootFiles, ProductFiles

Note Administrators working in managed environments can find complete resources for deploying Office updates in an organization at the Office Admin Update Center. At that site, scroll down and look under the Update Resources section for the software version you are updating. The Windows Installer Documentation also provides more information about the parameters supported by Windows Installer.

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 2.0 or later be installed on the system. All supported versions of Windows include Windows Installer 2.0 or a later version.

To install the 2.0 or later version of Windows Installer, visit one of the following Microsoft Web sites:

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/q Specifies quiet mode, or suppresses prompts, when files are being extracted.
/q:u Specifies user-quiet mode, which presents some dialog boxes to the user.
/q:a Specifies administrator-quiet mode, which does not present any dialog boxes to the user.
/t:path Specifies the target folder for extracting files.
/c Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder.
/c:path Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file.
/r:n Never restarts the system after installation.
/r:I Prompts the user to restart the system if a restart is required, except when used with /q:a.
/r:a Always restarts the system after installation.
/r:s Restarts the system after installation without prompting the user.
/n:v No version checking - Install the program over any earlier version.

Note You can combine these switches into one command. For backward compatibility, the security update also supports 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 Microsoft Office XP 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 versions and 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 click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

      Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
    5. On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.

      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.

Visio 2003 (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the Deployment Information subsection below.

Inclusion in Future Service Packs There are no more service packs planned for this software. The update for this issue may be included in a future update rollup.
Deployment
Installing without user interventionvisio2003-kb2434733-FullFile-ENU.exe /q:a
Installing without restartingvisio2003-kb2434733-FullFile-ENU.exe /r:n
Update log fileNot applicable
Further informationFor detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance. 

For features you can selectively install, see the Office Features for Administrative Installations subsection in this section.
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.
HotPatchingNot applicable
Removal Information Use Add or Remove Programs tool 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 tool 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 2434733
Registry Key Verification Not applicable

Office Features

The following table contains the list of feature names (case sensitive) that must be reinstalled for the update. To install all features, you can use REINSTALL=ALL or you can install the following features:

ProductFeature
VISVEA, VISPRO, VISPRORBuilding_Plan_Unitless, CAD_Drawing_Display_Unitless, Database_Design_Unitless,Organization_Charts_Unitless, Software_Design_Unitless, VisioCore
VISSTD, VISSTDRBuilding_Plan_Unitless, CAD_Drawing_Display_Unitless, Organization_Charts_Unitless, VisioCore

Note Administrators working in managed environments can find complete resources for deploying Office updates in an organization at the Office Admin Update Center. At that site, scroll down and look under the Update Resources section for the software version you are updating. The Windows Installer Documentation also provides more information about the parameters supported by Windows Installer.

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 2.0 or later be installed on the system. All supported versions of Windows include Windows Installer 2.0 or a later version.

To install the 2.0 or later version of Windows Installer, visit one of the following Microsoft Web sites:

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/q Specifies quiet mode, or suppresses prompts, when files are being extracted.
/q:u Specifies user-quiet mode, which presents some dialog boxes to the user.
/q:a Specifies administrator-quiet mode, which does not present any dialog boxes to the user.
/t:path Specifies the target folder for extracting files.
/c Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder.
/c:path Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file.
/r:n Never restarts the system after installation.
/r:I Prompts the user to restart the system if a restart is required, except when used with /q:a.
/r:a Always restarts the system after installation.
/r:s Restarts the system after installation without prompting the user.
/n:v No version checking - Install the program over any earlier version.

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 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 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.

    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.
    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.
    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.

Microsoft Visio 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 interventionvisio2007-kb2434737-fullfile-x86-glb.exe /passive
Installing without restartingvisio2007-kb2434737-fullfile-x86-glb.exe /norestart
Update log fileNot applicable
Further informationFor 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.
HotPatchingNot applicable
Removal Information Use Add or Remove Programs tool in Control Panel.
File Information See Microsoft Knowledge Base Article 2434737
Registry Key Verification Not applicable

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 be installed on the system.

To install the 3.1 or later version of Windows Installer, visit one of the following Microsoft Web sites:

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/? or /helpDisplays 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.

    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.
    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.
    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

Acknowledgments

Microsoft thanks the following for working with us to help protect customers:

  • Procyun, working with TippingPoint's Zero Day Initiative, for reporting the Visio Object Memory Corruption Vulnerability (CVE-2011-0092)
  • Xin Ouyang of Palo Alto Networks for reporting the Visio Object Memory Corruption Vulnerability (CVE-2011-0092)
  • Xin Ouyang of Palo Alto Networks for reporting the Visio Data Type Memory Corruption Vulnerability (CVE-2011-0093)

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 visit the active protections Web sites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners.

Support

  • Customers in the U.S. and Canada can receive technical support from Security Support or 1-866-PCSAFETY. 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 (February 8, 2011): Bulletin published.

Built at 2014-04-18T13:49:36Z-07:00

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.