Security Bulletin
Microsoft Security Bulletin MS12-022 - Important
Vulnerability in Expression Design Could Allow Remote Code Execution (2651018)
Published: March 13, 2012 | Updated: March 14, 2012
Version: 1.1
General Information
Executive Summary
This security update resolves one privately reported vulnerability in Microsoft Expression Design. The vulnerability could allow remote code execution if a user opens a legitimate file (such as an .xpr or .DESIGN file) that is located in the same network directory as a specially crafted dynamic link library (DLL) file. Then, while opening the legitimate file, Microsoft Expression Design could attempt to load the DLL file and execute any code it contained. For an attack to be successful, a user must visit an untrusted remote file system location or WebDAV share and open a legitimate file (such as an .xpr or .DESIGN file) from this location that is then loaded by a vulnerable application.
This security update is rated Important for all supported releases of Microsoft Expression Design. For more information, see the subsection, Affected and Non-Affected Software, in this section.
The security update addresses the vulnerability by correcting the manner in which Microsoft Expression Design loads external libraries. 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. The majority of customers have automatic updating enabled and will not need to take any action because this security update will be downloaded and installed automatically. Customers who have not enabled automatic updating need to check for updates and install this update manually. For information about specific configuration options in automatic updating, see Microsoft Knowledge Base Article 294871.
For administrators and enterprise installations, or end users who want to install this security update manually, Microsoft recommends that customers apply the update at the earliest opportunity using update management software, or by checking for updates using the Microsoft Update service.
See also the section, Detection and Deployment Tools and Guidance, later in this bulletin.
Known Issues. Microsoft Knowledge Base Article 2651018 documents the 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
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
| Software | Maximum Security Impact | Aggregate Severity Rating | Bulletins Replaced by this Update |
|---|---|---|---|
| Microsoft Expression Design\ (KB2675064) | Remote Code Execution | Important | None |
| Microsoft Expression Design Service Pack 1\ (KB2667724) | Remote Code Execution | Important | None |
| Microsoft Expression Design 2\ (KB2667725) | Remote Code Execution | Important | None |
| Microsoft Expression Design 3\ (KB2667727) | Remote Code Execution | Important | None |
| Microsoft Expression Design 4\ (KB2667730) | Remote Code Execution | Important | None |
Frequently Asked Questions (FAQ) Related to This Security Update
Where are the file information details?
Refer to the reference tables in the Security Update Deployment section for the location of the file information details.
Is this update related to Microsoft Security Advisory 2269637?
Yes, the vulnerability addressed by this update is related to the class of vulnerabilities, described in Microsoft Security Advisory 2269637, that affects how applications load external libraries. This security update addresses a particular instance of this type of vulnerability.
Vulnerability Information
Severity Ratings and Vulnerability Identifiers
The following severity ratings assume the potential maximum impact of the vulnerability. For information regarding the likelihood, within 30 days of this security bulletin's release, of the exploitability of the vulnerability in relation to its severity rating and security impact, please see the Exploitability Index in the March bulletin summary. For more information, see Microsoft Exploitability Index.
| Affected Software | Expression Design Insecure Library Loading Vulnerability - CVE-2012-0016 | Aggregate Severity Rating |
|---|---|---|
| Microsoft Expression Design | Important \ Remote Code Execution | Important |
| Microsoft Expression Design Service Pack 1 | Important \ Remote Code Execution | Important |
| Microsoft Expression Design 2 | Important \ Remote Code Execution | Important |
| Microsoft Expression Design 3 | Important \ Remote Code Execution | Important |
| Microsoft Expression Design 4 | Important \ Remote Code Execution | Important |
Expression Design Insecure Library Loading Vulnerability - CVE-2012-0016
A remote code execution vulnerability exists in the way that Microsoft Expression Design handles the loading of DLL files. An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2012-0016.
Mitigating Factors for Expression Design Insecure Library Loading Vulnerability - CVE-2012-0016
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:
- For an attack to be successful, a user must visit an untrusted remote file system location or WebDAV share and open a legitimate file (such as an .xpr or .DESIGN file) from this location that is then loaded by a vulnerable application.
- The file sharing protocol, Server Message Block (SMB), is often disabled on the perimeter firewall. This limits the potential attack vectors for this vulnerability.
- An attacker who successfully exploited this vulnerability could gain the same user rights as the logged-on user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
Workarounds for Expression Design Insecure Library Loading Vulnerability - CVE-2012-0016
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:
Disable loading of libraries from WebDAV and remote network shares
Note See Microsoft Knowledge Base Article 2264107 to deploy a workaround tool that allows customers to disable the loading of libraries from remote network or WebDAV shares. This tool can be configured to disallow insecure loading on a per-application or a global system basis.
Customers who are informed by their vendor of an application being vulnerable can use this tool to help protect against attempts to exploit this issue.
Note See Microsoft Knowledge Base Article 2264107 to use the automated Microsoft Fix it solution to deploy the registry key to block the loading of libraries for SMB and WebDAV shares. Note that this Fix it solution does require you to install the workaround tool also described in Microsoft Knowledge Base Article 2264107 first. This Fix it solution only deploys the registry key and requires the workaround tool in order to be effective. We recommend that administrators review the KB article closely prior to deploying this Fix it solution.
Disable the WebClient service
Disabling the WebClient service helps protect affected systems from attempts to exploit this vulnerability by blocking the most likely remote attack vector through the Web Distributed Authoring and Versioning (WebDAV) client service. After applying this workaround it is still possible for remote attackers who successfully exploit this vulnerability to cause the system to run programs located on the targeted user's computer or the Local Area Network (LAN), but users will be prompted for confirmation before opening arbitrary programs from the Internet.
To disable the WebClient Service, follow these steps:
- Click Start, click Run, type Services.msc and then click OK.
- Right-click WebClient service and select Properties.
- Change the Startup type to Disabled. If the service is running, click Stop.
- Click OK and exit the management application.
Impact of workaround. When the WebClient service is disabled, Web Distributed Authoring and Versioning (WebDAV) requests are not transmitted. In addition, any services that explicitly depend on the Web Client service will not start, and an error message will be logged in the System log. For example, WebDAV shares will be inaccessible from the client computer.
How to undo the workaround.
To re-enable the WebClient Service, follow these steps:
- Click Start, click Run, type Services.msc and then click OK.
- Right-click WebClient service and select Properties.
- Change the Startup type to Automatic. If the service is not running, click Start.
- Click OK and exit the management application.
Block TCP ports 139 and 445 at the firewall
These ports are used to initiate a connection with the affected component. Blocking TCP ports 139 and 445 at the firewall will help protect systems that are behind that firewall from attempts to exploit this vulnerability. Microsoft recommends that you block all unsolicited inbound communication from the Internet to help prevent attacks that may use other ports. For more information about ports, see the TechNet article, TCP and UDP Port Assignments.
Impact of workaround. Several Windows services use the affected ports. Blocking connectivity to the ports may cause various applications or services to not function. Some of the applications or services that could be impacted are listed below:
- Applications that use SMB (CIFS)
- Applications that use mailslots or named pipes (RPC over SMB)
- Server (File and Print Sharing)
- Group Policy
- Net Logon
- Distributed File System (DFS)
- Terminal Server Licensing
- Print Spooler
- Computer Browser
- Remote Procedure Call Locator
- Fax Service
- Indexing Service
- Performance Logs and Alerts
- Systems Management Server
- License Logging Service
How to undo the workaround. Unblock TCP ports 139 and 445 at the firewall. For more information about ports, see TCP and UDP Port Assignments.
FAQ for Expression Design Insecure Library Loading Vulnerability - CVE-2012-0016
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?
The vulnerability is caused when Microsoft Expression Design incorrectly restricts the path used for loading external libraries.
What is a Microsoft Expression Design Graphic (.xpr) file?
The Microsoft Expression Design Graphic (.xpr) file is a type of file created by Microsoft Expression Graphic Design (EGD), the predecessor to Microsoft Expression Design (ED); it stores a graphic that can be used as a user interface mockup. This file type was replaced by the .DESIGN file type in Expression Design.
What is a Microsoft Expression Design Drawing (.DESIGN) file?
The Microsoft Expression Design Drawing (.DESIGN) file is a type of file created by Microsoft Expression Design; it can contain both vector and raster graphics and can also include multiple layers and various image effects.
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. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. If a user is logged-on with administrative user rights, an attacker could take complete control of the affected system. 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?
An attacker could convince a user to open a legitimate Expression Design-related file (such as an .xpr or .DESIGN file) that is located in the same network directory as a specially crafted dynamic link library (DLL) file. Then, while opening the legitimate file, Expression Design could attempt to load the DLL file and execute any code it contained.
In an email attack scenario, an attacker could exploit the vulnerability by sending a legitimate Expression Design-related file (such as an .xpr or .DESIGN file) to a user, and convincing the user to place the attachment into a directory containing a specially crafted DLL file and to open the legitimate file. Then, while opening the legitimate file, Expression Design could attempt to load the DLL file and execute any code it contained.
In a network attack scenario, an attacker could place a legitimate Expression Design-related file and a specially crafted DLL in a network share, a UNC, or WebDAV location and then convince the user to open the file.
What systems are primarily at risk from the vulnerability?
Systems where Microsoft Expression Design 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?
The update addresses this vulnerability by correcting the manner in which Microsoft Expression Design loads external libraries.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through coordinated vulnerability disclosure.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.
Update Information
Detection and Deployment Tools and Guidance
Security Central
Manage the software and security updates you need to deploy to the servers, desktop, and mobile systems in your organization. For more information see the TechNet Update Management Center. The Microsoft TechNet Security website 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."
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 Expression Design | Yes |
| Microsoft Expression Design Service Pack 1 | Yes |
| Microsoft Expression Design 2 | Yes |
| Microsoft Expression Design 3 | Yes |
| Microsoft Expression Design 4 | Yes |
Note For customers using legacy software not supported by the latest release of MBSA, Microsoft Update, and Windows Server Update Services, please visit Microsoft Baseline Security Analyzer and reference the Legacy Product Support section on how to create comprehensive security update detection with legacy tools.
Windows Server Update Services
Windows Server Update Services (WSUS) enables information technology administrators to deploy the latest Microsoft product updates to computers that are running the Windows operating system. For more information about how to deploy security updates using Windows Server Update Services, see the TechNet article, Windows Server Update Services.
Systems Management Server
The following table provides the SMS detection and deployment summary for this security update.
| Software | SMS 2003 with ITMU | Configuration Manager 2007 |
|---|---|---|
| Microsoft Expression Design | Yes | Yes |
| Microsoft Expression Design Service Pack 1 | Yes | Yes |
| Microsoft Expression Design 2 | Yes | Yes |
| Microsoft Expression Design 3 | Yes | Yes |
| Microsoft Expression Design 4 | Yes | Yes |
Note Microsoft discontinued support for SMS 2.0 on April 12, 2011. For SMS 2003, Microsoft also discontinued support for the Security Update Inventory Tool (SUIT) on April 12, 2011. Customers are encouraged to upgrade to System Center Configuration Manager 2007. For customers remaining on SMS 2003 Service Pack 3, the Inventory Tool for Microsoft Updates (ITMU) is also an option.
For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, see SMS 2003 Inventory Tool for Microsoft Updates. For more information about SMS scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003.
System Center Configuration Manager 2007 uses WSUS 3.0 for detection of updates. For more information about Configuration Manager 2007 Software Update Management, visit System Center Configuration Manager 2007.
For more information about SMS, visit the SMS website.
For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles.
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 Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.
Security Update Deployment
Affected Software
For information about the specific security update for your affected software, click the appropriate link:
Microsoft Expression Design (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 | Not applicable |
|---|---|
| Deployment | |
| Installing without user intervention | Not applicable |
| Installing without restarting | For Microsoft Expression Design :\ KB2675064.exe /norestart |
| For Microsoft Expression Design Service Pack 1:\ KB2667724.exe /norestart | |
| Update log file | Not applicable |
| Further information | For detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance. |
| Restart Requirement | |
| Restart required? | This update may require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to allow the restart. |
| Hotpatching | Not applicable |
| Removal Information | This update cannot be uninstalled. |
| File Information | For Microsoft Expression Design:\ See Microsoft Knowledge Base Article 2675064 |
| For Microsoft Expression Design Service Pack 1:\ See Microsoft Knowledge Base Article 2667724 | |
| 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 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 the following Microsoft website:
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 | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| /? or /h or /help | Display usage dialog box. | ||||||||||||||
| Install Options | ** ** | ||||||||||||||
| /extract [directory] | Extract the package to the specified directory. | ||||||||||||||
| /uninstall or /u | Uninstall this update. | ||||||||||||||
| /addsource or /as | Specifies the source path of the product msi. This option may be used when installing the update results in a prompt to insert the installation source media for the product. For example:\ <update executable> /addsource "C:\Product MSI\Visual Studio\enu\vs_setup.msi" /addsource "C:\Product MSI\Net\Netfx.msi" | ||||||||||||||
| Restart Options | ** ** | ||||||||||||||
| /norestart | Do not restart after the installation is complete | ||||||||||||||
| /promptrestart | Prompts the user for restart if necessary | ||||||||||||||
| /forcerestart | Always restart the computer after installation | ||||||||||||||
| Logging Options | ** ** | ||||||||||||||
| /l[i | w | e | a | r | u | c | m | o | p | v | x | + | ! | *] <LogFile> | i - Status messages\ w - Nonfatal warnings\ e - All error messages\ a - Start up of actions\ r - Action-specific records\ u - User requests\ c - Initial UI parameters\ m - Out-of-memory or fatal exit information\ o - Out-of-disk-space messages\ p - Terminal properties\ v - Verbose output\ x - Extra debugging information\ + - Append to existing log file\ ! - Flush each line to the log\ * - Log all information, except for v and x options |
| /log <LogFile> | Equivalent of /l* <LogFile> | ||||||||||||||
| /sendreport | Send installation data for this update to Microsoft as a Watson report. No personally identifiable information is sent. |
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 item in Control Panel.
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 “Microsoft baseline Security Analyzer” heading under the section, Microsoft Detection and Deployment Tools and Guidance.
File Version Verification
Note 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 edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed. - 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.
Microsoft Expression Design 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 | Not applicable |
| Deployment | |
| Installing without user intervention | Not applicable |
| Installing without restarting | KB2667725.exe /norestart |
| Update log file | Not applicable |
| Further information | For detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance. |
| Restart Requirement | |
| Restart required? | This update may require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to allow the restart. |
| Hotpatching | Not applicable |
| Removal Information | This update cannot be uninstalled. |
| File Information | See Microsoft Knowledge Base Article 2667725 |
| 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 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 the following Microsoft website:
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 | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| /? or /h or /help | Display usage dialog box. | ||||||||||||||
| Install Options | ** ** | ||||||||||||||
| /extract [directory] | Extract the package to the specified directory. | ||||||||||||||
| /uninstall or /u | Uninstall this update. | ||||||||||||||
| /addsource or /as | Specifies the source path of the product msi. This option may be used when installing the update results in a prompt to insert the installation source media for the product. For example:\ <update executable> /addsource "C:\Product MSI\Visual Studio\enu\vs_setup.msi" /addsource "C:\Product MSI\Net\Netfx.msi" | ||||||||||||||
| Restart Options | ** ** | ||||||||||||||
| /norestart | Do not restart after the installation is complete | ||||||||||||||
| /promptrestart | Prompts the user for restart if necessary | ||||||||||||||
| /forcerestart | Always restart the computer after installation | ||||||||||||||
| Logging Options | ** ** | ||||||||||||||
| /l[i | w | e | a | r | u | c | m | o | p | v | x | + | ! | *] <LogFile> | i - Status messages\ w - Nonfatal warnings\ e - All error messages\ a - Start up of actions\ r - Action-specific records\ u - User requests\ c - Initial UI parameters\ m - Out-of-memory or fatal exit information\ o - Out-of-disk-space messages\ p - Terminal properties\ v - Verbose output\ x - Extra debugging information\ + - Append to existing log file\ ! - Flush each line to the log\ * - Log all information, except for v and x options |
| /log <LogFile> | Equivalent of /l* <LogFile> | ||||||||||||||
| /sendreport | Send installation data for this update to Microsoft as a Watson report. No personally identifiable information is sent. |
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 item in Control Panel.
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 “Microsoft baseline Security Analyzer” heading under the section, Microsoft Detection and Deployment Tools and Guidance.
File Version Verification
Note 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 edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed. - 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.
Microsoft Expression Design 3
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 | Not applicable |
|---|---|
| Deployment | |
| Installing without user intervention | Not applicable |
| Installing without restarting | KB2667727.exe /norestart |
| Update log file | Not applicable |
| Further information | For detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance. |
| Restart Requirement | |
| Restart required? | This update may require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to allow the restart. |
| Hotpatching | Not applicable |
| Removal Information | Use Add or Remove Programs item in Control Panel. |
| File Information | See Microsoft Knowledge Base Article 2667727 |
| Registry Key Verification | For Microsoft Expression Design 3 on 32-bit operating systems:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{9981CE5A-87DB-4AB1-99CC-E0D55EB8AA82}\ For Microsoft Expression Design 3 on 64-bit operating systems:\ HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall{9981CE5A-87DB-4AB1-99CC-E0D55EB8AA82} |
Deployment Information
Installing the Update
When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
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 | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| /? or /h or /help | Display usage dialog box. | ||||||||||||||
| Install Options | ** ** | ||||||||||||||
| /extract [directory] | Extract the package to the specified directory. | ||||||||||||||
| /uninstall or /u | Uninstall this update. | ||||||||||||||
| /addsource or /as | Specifies the source path of the product msi. This option may be used when installing the update results in a prompt to insert the installation source media for the product. For example:\ <update executable> /addsource "C:\Product MSI\Visual Studio\enu\vs_setup.msi" /addsource "C:\Product MSI\Net\Netfx.msi" | ||||||||||||||
| Restart Options | ** ** | ||||||||||||||
| /norestart | Do not restart after the installation is complete | ||||||||||||||
| /promptrestart | Prompts the user for restart if necessary | ||||||||||||||
| /forcerestart | Always restart the computer after installation | ||||||||||||||
| Logging Options | ** ** | ||||||||||||||
| /l[i | w | e | a | r | u | c | m | o | p | v | x | + | ! | *] <LogFile> | i - Status messages\ w - Nonfatal warnings\ e - All error messages\ a - Start up of actions\ r - Action-specific records\ u - User requests\ c - Initial UI parameters\ m - Out-of-memory or fatal exit information\ o - Out-of-disk-space messages\ p - Terminal properties\ v - Verbose output\ x - Extra debugging information\ + - Append to existing log file\ ! - Flush each line to the log\ * - Log all information, except for v and x options |
| /log <LogFile> | Equivalent of /l* <LogFile> | ||||||||||||||
| /sendreport | Send installation data for this update to Microsoft as a Watson report. No personally identifiable information is sent. |
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.
Verifying That the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
- Click Start and then enter an update file name in the Start Search box.
- When the file appears under Programs, right-click the file name and click Properties.
- On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed. - You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation. - Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
Microsoft Expression Design 4
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 | Not applicable |
|---|---|
| Deployment | |
| Installing without user intervention | Not applicable |
| Installing without restarting | KB2667730.exe /norestart |
| Update log file | Not applicable |
| Further information | For detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance. |
| Restart Requirement | |
| Restart required? | This update may require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to allow the restart. |
| Hotpatching | Not applicable |
| Removal Information | Use Add or Remove Programs item in Control Panel. |
| File Information | See Microsoft Knowledge Base Article 2667730 |
| Registry Key Verification | For Microsoft Expression Design 4 on 32-bit operating systems:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{84B3B987-43ED-4AF5-B9D9-BD64693EC100}\ For Microsoft Expression Design 4 on 64-bit operating systems:\ HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall{84B3B987-43ED-4AF5-B9D9-BD64693EC100} |
Deployment Information
Installing the Update
When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
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 | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| /? or /h or /help | Display usage dialog box. | ||||||||||||||
| Install Options | ** ** | ||||||||||||||
| /extract [directory] | Extract the package to the specified directory. | ||||||||||||||
| /uninstall or /u | Uninstall this update. | ||||||||||||||
| /addsource or /as | Specifies the source path of the product msi. This option may be used when installing the update results in a prompt to insert the installation source media for the product. For example:\ <update executable> /addsource "C:\Product MSI\Visual Studio\enu\vs_setup.msi" /addsource "C:\Product MSI\Net\Netfx.msi" | ||||||||||||||
| Restart Options | ** ** | ||||||||||||||
| /norestart | Do not restart after the installation is complete | ||||||||||||||
| /promptrestart | Prompts the user for restart if necessary | ||||||||||||||
| /forcerestart | Always restart the computer after installation | ||||||||||||||
| Logging Options | ** ** | ||||||||||||||
| /l[i | w | e | a | r | u | c | m | o | p | v | x | + | ! | *] <LogFile> | i - Status messages\ w - Nonfatal warnings\ e - All error messages\ a - Start up of actions\ r - Action-specific records\ u - User requests\ c - Initial UI parameters\ m - Out-of-memory or fatal exit information\ o - Out-of-disk-space messages\ p - Terminal properties\ v - Verbose output\ x - Extra debugging information\ + - Append to existing log file\ ! - Flush each line to the log\ * - Log all information, except for v and x options |
| /log <LogFile> | Equivalent of /l* <LogFile> | ||||||||||||||
| /sendreport | Send installation data for this update to Microsoft as a Watson report. No personally identifiable information is sent. |
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.
Verifying That the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
- Click Start and then enter an update file name in the Start Search box.
- When the file appears under Programs, right-click the file name and click Properties.
- On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed. - You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation. - Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
Other Information
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
- Laplinker for reporting the Expression Design Insecure Library Loading Vulnerability (CVE-2012-0016)
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 websites 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 (1-866-727-2338). For more information about available support options, see Microsoft Help and Support.
- International customers can receive support from their local Microsoft subsidiaries. For more information about how to contact Microsoft for support issues, visit the International Support website.
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 (March 13, 2012): Bulletin published.
- V1.1 (March 14, 2012): Removed erroneous installation switch option descriptions from the Security Update Deployment tables for all supported releases. This is an informational change only. There were no changes to the detection logic or the update files.
Built at 2014-04-18T13:49:36Z-07:00