Security Bulletin
Microsoft Security Bulletin MS07-030 - Important
Vulnerabilities in Microsoft Visio Could Allow Remote Code Execution (927051)
Published: June 12, 2007 | Updated: January 16, 2008
Version: 1.1
General Information
Executive Summary
This important update resolves two privately reported vulnerabilities in addition to other security issues identified during the course of the investigation. The privately reported vulnerabilities could allow remote code execution if a user opened a specially crafted Visio file. 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. User interaction is required to exploit these vulnerabilities.
This is an important security update for supported versions of Microsoft Visio 2002 and Microsoft Office Visio 2003. For more information, see the subsection, Affected and Non-Affected Software, in this section.
This security update addresses the vulnerabilities by modifying the way that Microsoft Visio handles specially crafted Visio files. For more information about the vulnerabilities, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.
Recommendation. Microsoft recommends that customers should apply the update at the earliest opportunity.
Known Issues. Microsoft Knowledge Base Article 927051 documents currently known issues that customers may experience when installing this security update. The article also documents recommended solutions for these issues.
Affected and Non-Affected Software
In the following tables of affected and non-affected software, software versions that are not listed are past their support lifecycle. To determine the support lifecycle for your product and version, visit Microsoft Support Lifecycle.
Affected Software
| Office Suite and Other Affected Software | Application | Maximum Security Impact | Aggregate Severity Rating | Bulletins Replaced by This Update |
|---|---|---|---|---|
| Microsoft Visio 2002 Service Pack 2 | Remote Code Execution | Important | None | |
| Microsoft Office 2003 | Microsoft Visio 2003 Service Pack 2 | Remote Code Execution | Important | None |
Non-Affected Software
| Office Suite | Application |
|---|---|
| 2007 Microsoft Office System | Microsoft Office Visio 2007 |
Frequently Asked Questions (FAQ) Related to This Security Update
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 can install only this update.
I am using an older version of the software discussed in this security bulletin. What should I do?
The affected software listed in this bulletin has been tested to determine which versions are affected. Other versions are past their support life cycle. To determine the support life cycle for your product and version, visit Microsoft Support Lifecycle.
It should be a priority for customers who have older versions of the software to migrate to supported versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the following Microsoft Support Lifecycle. For more information about the extended security update support period for these operating system versions, visit the Microsoft Product Support Services Web site.
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, 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 Windows Operating System Product Support Lifecycle FAQ.
Vulnerability Information
Severity Ratings and Vulnerability Identifiers
| Affected Software | Visio Version Memory Corruption Vulnerability - CVE-2007-0934 | Visio Document Packaging Vulnerability - CVE-2007-0936 | Aggregate Severity Rating |
|---|---|---|---|
| Microsoft Visio 2002 | ImportantRemote Code Execution | ImportantRemote Code Execution | Important |
| Microsoft Visio 2003 | ImportantRemote Code Execution | ImportantRemote Code Execution | Important |
Version Number Memory Corruption Vulnerability - CVE-2007-0934
A remote code execution vulnerability exists in the way Microsoft Visio handles a specially crafted version number in a Visio (.VSD, VSS, or .VST) file. An attacker could exploit this vulnerability when Visio does not correctly validate the version number field when processing the contents of a file. Such a specially crafted file might be included as an e-mail attachment, or hosted on a malicious or compromised Web site.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2007-0934.
Mitigating Factors for Version Number Memory Corruption Vulnerability - CVE-2007-0934
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 Web page that is used to exploit this vulnerability In addition, Web sites that accept or host user-provided content, or compromised Web sites and advertisement servers 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 persuade 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.
- An attacker who successfully exploited this vulnerability could gain the same user rights as the local 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.
- Microsoft Office Visio 2007 is not affected by this vulnerability.
Workarounds for Version Number Memory Corruption Vulnerability - CVE-2007-0934
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:
- Use Microsoft Visio Viewer 2003 or Microsoft Visio Viewer 2007 to open and view files. Microsoft Visio Viewer 2003 and Microsoft Visio Viewer 2007 are not affected by the issue. Users can download the Microsoft Visio Viewer 2003 and Microsoft Visio Viewer 2007 from the Microsoft Download Center.
- Do not open or save Microsoft Visio files that you receive from untrusted sources or that you receive unexpectedly from trusted sources.
FAQ for Version Number Memory Corruption Vulnerability - CVE-2007-0934
What is the scope of the vulnerability?
A remote code execution vulnerability exists in Microsoft Visio. An attacker could exploit this vulnerability could remotely take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
What causes the vulnerability?
Microsoft Visio does not correctly validate the version number field when processing version related data of a file.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could run arbitrary code on a user’s system. This could allow an attacker to take complete control of the affected system.
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 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 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 a specially crafted Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site.
What systems are primarily at risk from the vulnerability?
Workstations and terminal servers that have Microsoft Visio installed are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.
What does the update do?
The update removes the vulnerability by modifying the way that Microsoft Visio handles the validation of Visio file version related data.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued. This security bulletin addresses the privately disclosed vulnerability as well as additional issues discovered through internal investigations.
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 and had not seen any examples of proof of concept code published when this security bulletin was originally issued.
Visio Document Packaging Vulnerability - CVE-2007-0936
A remote code execution vulnerability exists in Microsoft Visio as a result of the way it incorrectly handles the parsing of packed objects within the Visio file format. An attacker could exploit this vulnerability by constructing a malicious Visio (.VSD, VSS, or .VST) file that could potentially allow remote code execution if a user visited a malicious Web site or opened a specially crafted Visio attachment included in an e-mail message. An attacker who successfully exploited this vulnerability could take complete control of an affected system.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2007-0936.
Mitigating Factors for Visio Document Packaging Vulnerability - CVE-2007-0936
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 Web page that is used to exploit this vulnerability In addition, Web sites that accept or host user-provided content, or compromised Web sites and advertisement servers 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 persuade 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.
- An attacker who successfully exploited this vulnerability could gain the same user rights as the local 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.
- Microsoft Office Visio 2007 is not affected by this vulnerability.
Workarounds for Visio Document Packaging Vulnerability - CVE-2007-0936
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:
- Use Microsoft Visio Viewer 2003 or Microsoft Visio Viewer 2007 to open and view files. Microsoft Visio Viewer 2003 and Microsoft Visio Viewer 2007 are not affected by the issue. Users can download the Microsoft Visio Viewer 2003 and Microsoft Visio Viewer 2007 from the Microsoft Download Center.
- Do not open or save Microsoft 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 Document Packaging Vulnerability - CVE-2007-0936
What is the scope of the vulnerability?
A remote code execution vulnerability exists in Microsoft Visio. An attacker who successfully exploited this vulnerability could remotely take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
What causes the vulnerability?
Visio incorrectly handles the parsing of a packed object resulting in memory corruption.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could cause arbitrary code to run with the privileges of the user who opened the file.
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 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 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 a specially crafted Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site.
What systems are primarily at risk from the vulnerability?
Workstations and terminal servers that have Microsoft Visio installed are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.
What does the update do?
The update removes the vulnerability by modifying the way that Visio validates packaging and parsing related data in a Visio file (.VSS, .VSD, or .VST) file.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued. This security bulletin addresses the privately disclosed vulnerability as well as additional issues discovered through internal investigations.
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 and had not seen any examples of proof of concept code published when this security bulletin was originally issued.
Update Information
Detection and Deployment Tools and Guidance
Manage the software and security updates you need to deploy to the servers, desktop, and mobile systems in your organization. For more information see the TechNet Update Management Center. The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.
Security updates are available from Microsoft Update, Windows Update, and Office Update. Security updates are also available at the Microsoft Download Center. You can find them most easily by doing a keyword search for "security_patch." Finally, security updates can be downloaded from the Windows Update Catalog. For more information about the Windows Update Catalog, see Microsoft Knowledge Base Article 323166.
Detection and Deployment Guidance
Microsoft has provided detection and deployment guidance for this month’s security updates. This guidance will also help IT professionals understand how they can use various tools to help deploy the security update, such as Windows Update, Microsoft Update, Office Update, the Microsoft Baseline Security Analyzer (MBSA), the Office Detection Tool, Microsoft Systems Management Server (SMS), the Extended Security Update Inventory Tool, and the Enterprise Update Scan Tool (EST). For more information, see Microsoft Knowledge Base Article 910723.
Microsoft Baseline Security Analyzer
Microsoft Baseline Security Analyzer (MBSA) allows administrators to scan local and remote systems for missing security updates as well as common security misconfigurations. For more information about MBSA visit Microsoft Baseline Security Analyzer Web site. The following table provides the MBSA detection summary for this security update.
| Software | MBSA 1.2.1 | MBSA 2.0.1 |
|---|---|---|
| Microsoft Visio 2002 | Yes | Yes |
| Microsoft Visio 2003 | Yes | Yes |
For more information about MBSA, visit the MBSA Web site. For more information about the software that Microsoft Update and MBSA 2.0 currently do not detect, see Microsoft Knowledge Base Article 895660.
Note MBSA 1.2.1 uses an integrated version of the Office Detection Tool (ODT) which does not support remote scans of this security update. For more information about MBSA, visit the MBSA Web site.
Windows Server Update Services
By using Windows Server Update Services (WSUS), administrators can deploy the latest critical updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000 to Windows 2000 and later operating systems. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site.
Systems Management Server
The following table provides the SMS detection and deployment summary for this security update.
| Product | SMS 2.0 | SMS 2003 |
|---|---|---|
| Microsoft Visio 2002 | Yes | Yes |
| Microsoft Visio 2003 | Yes | Yes |
SMS 2.0 and SMS 2003 Software Update Services (SUS) Feature Pack can use MBSA 1.2.1 for detection and therefore have the same limitation that is listed earlier in this bulletin related to programs that MBSA 1.2.1 does not detect.
For SMS 2.0, the SMS SUS Feature Pack, which includes the Security Update Inventory Tool (SUIT), can be used by SMS to detect security updates. SMS SUIT uses the MBSA 1.2.1 engine for detection. For more information about SUIT, visit the following Microsoft Web site. For more information about the limitations of SUIT, see Microsoft Knowledge Base Article 306460. The SMS SUS Feature Pack also includes the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.
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, visit the following Microsoft Web site. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.
For more information about SMS, visit the SMS Web site.
Note If you have used an Administrative Installation Point (AIP) for deploying Office 2000, Office XP or Office 2003, you may not be able to deploy the update using SMS if you have updated the AIP from the original baseline. For more information, see the Office Administrative Installation Point heading in this section.
Office Administrative Installation Point
If you installed your application from a server location, the server administrator must update the server location with the administrative update and deploy that update to your system.
For supported versions of Microsoft Office XP, see Creating an Administrative Installation Point. For more information on how to change the source for a client system from an updated administrative installation point to an Office XP original baseline source or Service Pack 3 (SP3), see Microsoft Knowledge Base Article 922665.
Note. If you plan to manage software updates centrally from an updated administrative image, you can find more information in the article Updating Office XP Clients from a Patched Administrative Image.
For supported versions of Microsoft Office 2003, see Creating an Administrative Installation Point. If you have an Administrative Installation Point with a non-supported version of Microsoft Office 2003, see Microsoft Knowledge Base Article 902349.
Note. If you plan to manage software updates centrally from an updated administrative image, you can find more information in the article Distributing Office 2003 Product Updates. For supported versions of the 2007 Microsoft Office system, see Create a network installation point for the 2007 Office system.
Note. If you plan to manage security updates centrally use Windows Server Update Services. For more information about how to deploy security updates for the 2007 Microsoft Office system using Windows Server Update Services, visit the Windows Server Update Services Web site.
Security Update Deployment
Affected Software
For information about the specific security update for your affected software, click the appropriate section:
Visio 2002 Service Pack 2
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 intervention | Visio2002-KB931280-FullFile-ENU.exe /q:a |
| Installing without restarting | Visio2002-KB931280-FullFile-ENU.exe /r:n |
| Update log file | Not applicable |
| Further information | For detection and deployment, see the subsection, **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 | 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 | After you install the update, you cannot remove it. To revert to an installation before the update was installed; you must remove the application, and then install it again from the original media. |
| File Information | See the subsection, File Information, in this section, for the full file manifest. |
| Registry Key Verification | Not applicable |
File Information
The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
For all supported editions of Visio 2002:
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| Dfdc.dll | 10.0.6861.4 | 06-Mar-2007 | 04:14 | 1,462,272 |
| Dwgcnvt.dll | 10.0.6861.4 | 05-Mar-2007 | 17:38 | 2,600,960 |
| Umlc.dll | 10.0.6861.4 | 06-Mar-2007 | 04:06 | 1,441,792 |
| Umlsystem.dll | 10.0.6861.4 | 06-Mar-2007 | 20:05 | 548,864 |
| Visio.exe | 10.0.6865.4 | 22-Mar-2007 | 04:26 | 71,592 |
| Visiodwg.dll | 10.0.6861.4 | 05-Mar-2007 | 19:14 | 2,428,928 |
| Vislib.dll | 10.0.6865.4 | 22-Mar-2007 | 04:26 | 6,379,432 |
Note For a complete list of supported versions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.
Office Features for Administrative Installations
Server administrators who use a Windows Installer Administrative Installation must update the server location. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and deployment Tools and Guidance subsection.
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:
| Product | Feature |
|---|---|
| Visio 2002 | Program_Files, CAD_Drawing_Display,CAD_Drawing_Display_US,Software_Design, Software_Design_US |
Note Administrators working in managed environments can find 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 setup switches 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.
Note. 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 latest version of Windows Installer, visit one of the following Microsoft Web sites:
- Windows Installer 3.1 Redistributable
- Windows Installer 2.0Redistributable for Windows 2000 and Windows NT 4.0
- Windows Installer 2.0Redistributable for Windows 95, Windows 98, Windows 98 SE, and Windows Millennium Edition
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.
| Switch | Description |
|---|---|
| /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. For more information about the Package Installer, visit the Microsoft TechNet Web site. For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
Removing the Update
After you install the update, you cannot remove it. To revert to an installation before the update was installed; you must remove the application, and then install it again from the original media.
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.Click Start, and then click Search.
In the Search Results pane, click All files and folders under Search Companion.
In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
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.
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 Service Pack 2
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 | Visio2003-KB931281-FullFile-ENU.exe /q:a |
| Installing without restarting | Visio2003-KB931281-FullFile-ENU.exe /r:n |
| Update log file | Not applicable |
| Further information | For detection and deployment, see the subsection, **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 | 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.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. |
| File Information | See the subsection, File Information, in this section for the full file manifest |
| Registry Key Verification | Not applicable |
File Information
The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
For all supported editions of Office 2003:
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| Aec.dll | 11.0.5824.0 | 28-Oct-2005 | 07:41 | 863,016 |
| Dwgcnv.dll | 11.0.7212.0 | 31-Jan-2007 | 08:00 | 154,072 |
| Dwgdp.dll | 11.0.7212.0 | 31-Jan-2007 | 08:01 | 2,095,576 |
| Modeleng.dll | 11.0.6301.0 | 01-Mar-2006 | 14:10 | 477,952 |
| Orgchwiz.dll | 11.0.7117.0 | 28-Nov-2006 | 18:20 | 462,704 |
| Uml.dll | 11.0.7212.0 | 30-Jan-2007 | 08:34 | 1,496,576 |
| Umlsys.dll | 11.0.7212.0 | 30-Jan-2007 | 08:29 | 543,744 |
| Visio.exe | 11.0.6301.0 | 01-Mar-2006 | 14:09 | 187,072 |
| Vislib.dll | 11.0.7218.0 | 22-Mar-2007 | 15:21 | 8,285,624 |
Note For a complete list of supported versions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.
Office Features for Administrative Installations
Server administrators who use a Windows Installer Administrative Installation must update the server location. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and deployment Tools and Guidance subsection.
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:
| Product | Feature |
|---|---|
| Visio 2003 Standard | Building_Plan_Unitless, CAD_Drawing_Display_Unitless, Organization_Charts_Unitless, VisioCore |
| Visio for Enterprise Architects, Visio 2003 Professional | Building_Plan_Unitless, CAD_Drawing_Display_Unitless, Database_Design_Unitless,Organization_Charts_Unitless, Software_Design_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 setup switches 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.
Note. 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 latest version of Windows Installer, visit one of the following Microsoft Web sites:
- Windows Installer 3.1 Redistributable
- Windows Installer 2.0Redistributable for Windows 2000 and Windows NT 4.0
- Windows Installer 2.0Redistributable for Windows 95, Windows 98, Windows 98 SE, and Windows Millennium Edition
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.
| Switch | Description |
|---|---|
| /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. For more information about the Package Installer, visit the Microsoft TechNet Web site.
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.Click Start, and then click Search.
In the Search Results pane, click All files and folders under Search Companion.
In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
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.
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.
Other Information
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
Chris Ries of Vigilant Minds for reporting the Visio Document Packaging Vulnerability - (CVE-2007-0936).
Support
- Customers in the U.S. and Canada can receive technical support from Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates.
- International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site.
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 (June 12, 2007): Bulletin published.
- V1.1 (January 16, 2008): Bulletin updated to add KB article information to the Known Issues area of the General Information section.
Built at 2014-04-18T13:49:36Z-07:00