Article
06/08/2023

Security Bulletin

Microsoft Security Bulletin MS08-070 - Critical

Vulnerabilities in Visual Basic 6.0 Runtime Extended Files (ActiveX Controls) Could Allow Remote Code Execution (932349)

Published: December 09, 2008 | Updated: February 11, 2009

Version: 1.2

General Information

Executive Summary

This security update resolves five privately reported vulnerabilities and one publicly disclosed vulnerability in the ActiveX controls for the Microsoft Visual Basic 6.0 Runtime Extended Files. These vulnerabilities could allow remote code execution if a user browsed a Web site that contains specially crafted content. 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 Critical for supported components of the Microsoft Visual Basic 6.0 Runtime Extended Files; all supported editions of Microsoft Visual Studio .NET 2002, Microsoft Visual Studio .NET 2003, Microsoft Visual FoxPro 8.0, Microsoft Visual FoxPro 9.0, Microsoft Office Project 2003, Microsoft Office Project 2007; and the Chinese Simplified (China), Chinese Pan (Hong Kong), Chinese Traditional (Taiwan), and Korean versions of Microsoft Office FrontPage 2002. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses the vulnerabilities by improving validation and error handling within the ActiveX controls. 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 apply the update immediately.

Known Issues. Microsoft Knowledge Base Article 932349 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 Developer Tools
Microsoft Visual Basic 6.0 Runtime Extended Files (KB926857)	Remote Code Execution	Critical	None
Microsoft Visual Studio .NET 2002 Service Pack 1 (KB958392)	Remote Code Execution	Critical	None
Microsoft Visual Studio .NET 2003 Service Pack 1 (KB958393)	Remote Code Execution	Critical	None
Microsoft Visual FoxPro 8.0 Service Pack 1 (KB958369)	Remote Code Execution	Critical	None
Microsoft Visual FoxPro 9.0 Service Pack 1 (KB958370)	Remote Code Execution	Critical	None
Microsoft Visual FoxPro 9.0 Service Pack 2 (KB958371)	Remote Code Execution	Critical	None
Microsoft Office Software
Microsoft Office FrontPage 2002 Service Pack 3* (KB957797)	Remote Code Execution	Critical	None
Microsoft Office Project 2003 Service Pack 3 (KB949045)	Remote Code Execution	Critical	None
Microsoft Office Project 2007 (KB949046) Microsoft Office Project 2007 Service Pack 1 (KB949046)	Remote Code Execution	Critical	None

*This update only applies to FrontPage 2002 Service Pack 3 versions in Chinese Simplified (China), Chinese Pan (Hong Kong), Chinese Traditional (Taiwan), and Korean.

Non-Affected Software

Software
Microsoft Visual Studio 2005 Service Pack 1
Microsoft Visual Studio 2008
Microsoft Visual Studio 2008 Service Pack 1
Microsoft Office FrontPage 2000 Service Pack 3
Microsoft Office FrontPage 2003 Service Pack 3
Microsoft Expression Web
Microsoft Expression Web 2
Microsoft Project 2000 Service Release 1
Microsoft Project 2002 Service Pack 1
Microsoft Office Project Server 2003 Service Pack 3
Microsoft Office Project Portfolio Server 2007
Microsoft Office Project Portfolio Server 2007 Service Pack 1
Microsoft Office Project Server 2007
Microsoft Office Project Server 2007 Service Pack 1

Microsoft has released a cumulative update for Microsoft Visual Basic 6.0 Service Pack 6 (KB957924). What is the relationship between the cumulative update and the security update (KB926857) provided in this bulletin (MS08-070)?
Microsoft has released a cumulative update for Microsoft Visual Basic 6.0 Service Pack 6 that includes the security update for Microsoft Visual Basic 6.0 Runtime Extended Files (KB926857) provided in this bulletin. The cumulative update is available on the Microsoft Download Center. For more information about the cumulative update, see Microsoft Knowledge Base Article 957924.

Where are the file information details?
The file information details can be found in Microsoft Knowledge Base Article 932349.

What are the Visual Basic 6.0 Runtime Extended Files?
The Visual Basic 6.0 Runtime Extended Files include select ActiveX controls, libraries, and tools delivered with the Visual Basic 6.0 Integrated Development Environment (IDE) media and as an online release. Typically, either Visual Basic 6.0 IDE or Microsoft.com installs these files on the development system. The developer then redistributes these files with their applications. Although, as of April 8, 2008, support for Visual Basic 6.0 IDE has ended, Microsoft still offers support for select runtime extended files that are distributed with applications. For more information on support for the Visual Basic 6.0 Runtime Extended Files, please see Support Statement for Visual Basic 6.0 on Windows Vista and Windows Server 2008.

I am a third-party application developer and I use the ActiveX control in my application. Is my application vulnerable and how do I update it?
Developers who redistribute the ActiveX control should ensure that they update the version of the ActiveX control installed with their application by downloading the update provided in this bulletin. For more information on best practices on redistributed component use, please see Microsoft Knowledge Base Article 835322 and Isolated Applications and Side-by-side Assemblies.

I am developing software which contains the redistributable ActiveX control. What do I do?
You should install the security update included in this security bulletin for your development software. If you have redistributed ActiveX control with your application, you should issue an updated version of your application to your customers with the updated version of this file included in the download of this security update for your development software.

What are the known issues that customers may experience when installing this security update?
Microsoft Knowledge Base Article 932349 documents the currently known issues that customers may experience when they install this security update. The article also documents recommended solutions for these issues.

Does this update contain any security-related changes to functionality?
Yes. Besides the changes that are listed in the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the section, Vulnerability Information, this update includes a defense-in-depth change to the Winsock Control, mswinsck.ocx. This change involves setting the kill bit for the class ID with a value of {248dd896-bb45-11cf-9abc-0080c7e7b78d}.

By default, Internet Explorer will not instantiate the Winsock ActiveX Control as it is not marked as safe for scripting. Thus, by default, customers are not at risk from a Web-based attack. However, customers may be at risk via third-party applications that distribute and use mswinsck.ocx.

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. To determine the support life cycle for your software release, visit Microsoft Support Lifecycle.

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. For more information about the Windows Product Lifecycle, visit Microsoft Support Lifecycle. For more information about the extended security update support period for these software versions or editions, visit Microsoft Product Support Services.

Customers who require custom support for older releases 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 Microsoft Worldwide Information, 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	DataGrid Control Memory Corruption Vulnerability - CVE-2008-4252	FlexGrid Control Memory Corruption Vulnerability - CVE-2008-4253	Hierarchical FlexGrid Control Memory Corruption Vulnerability - CVE-2008-4254	Windows Common AVI Parsing Overflow Vulnerability - CVE-2008-4255	Charts Control Memory Corruption Vulnerability - CVE-2008-4256	Masked Edit Control Memory Corruption Vulnerability - CVE-2008-3704	Aggregate Severity Rating
Microsoft Developer Tools
Microsoft Visual Basic 6.0 Runtime Extended Files	Critical Remote Code Execution	Critical Remote Code Execution	Critical Remote Code Execution	Critical Remote Code Execution	Critical Remote Code Execution	Critical Remote Code Execution	Critical
Microsoft Visual Studio .NET 2002 Service Pack 1	Not applicable	Not applicable	Not applicable	Critical Remote Code Execution	Critical Remote Code Execution	Critical Remote Code Execution	Critical
Microsoft Visual Studio .NET 2003 Service Pack 1	Not applicable	Not applicable	Not applicable	Critical Remote Code Execution	Critical Remote Code Execution	Critical Remote Code Execution	Critical
Microsoft Visual FoxPro 8.0 Service Pack 1	Critical Remote Code Execution	Critical Remote Code Execution	Critical Remote Code Execution	Critical Remote Code Execution	Critical Remote Code Execution	Critical Remote Code Execution	Critical
Microsoft Visual FoxPro 9.0 Service Pack 1	Critical Remote Code Execution	Critical Remote Code Execution	Critical Remote Code Execution	Critical Remote Code Execution	Critical Remote Code Execution	Critical Remote Code Execution	Critical
Microsoft Visual FoxPro 9.0 Service Pack 2	Critical Remote Code Execution	Critical Remote Code Execution	Critical Remote Code Execution	Critical Remote Code Execution	Critical Remote Code Execution	Critical Remote Code Execution	Critical
Microsoft Office Software
Microsoft Office FrontPage 2002 Service Pack 3	Not applicable	Critical Remote Code Execution	Not applicable	Not applicable	Not applicable	Not applicable	Critical
Microsoft Office Project 2003 Service Pack 3	Not applicable	Critical Remote Code Execution	Not applicable	Critical Remote Code Execution	Not applicable	Not applicable	Critical
Microsoft Office Project 2007 and Microsoft Office Project 2007 Service Pack 1	Not applicable	Not applicable	Not applicable	Critical Remote Code Execution	Not applicable	Not applicable	Critical

DataGrid Control Memory Corruption Vulnerability - CVE-2008-4252

A remote code execution vulnerability exists in the DataGrid ActiveX Control for Visual Basic 6. An attacker could exploit the vulnerability by constructing a specially crafted Web page. When a user views the Web page, the vulnerability could allow remote code execution. An attacker who successfully exploited this vulnerability could gain the same user rights as the logged-on user.

To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2008-4252.

Mitigating Factors for DataGrid Control Memory Corruption Vulnerability - CVE-2008-4252

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, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker’s Web site.
By default, Internet Explorer on Windows Server 2003 and Windows Server 2008 runs in a restricted mode that is known as Enhanced Security Configuration. This mode sets the security level for the Internet zone to High. This is a mitigating factor for Web sites that you have not added to the Internet Explorer Trusted sites zone. See the FAQ subsection of this vulnerability section for more information about Internet Explorer Enhanced Security Configuration.
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.
By default, all supported versions of Microsoft Outlook and Microsoft Outlook Express open HTML e-mail messages in the Restricted sites zone. The Restricted sites zone helps mitigate attacks that could try to exploit this vulnerability by preventing Active Scripting and ActiveX controls from being used when reading HTML e-mail messages. However, if a user clicks a link in an e-mail message, the user could still be vulnerable to exploitation of this vulnerability through the Web-based attack scenario.

Workarounds for DataGrid Control Memory Corruption Vulnerability - CVE-2008-4252

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:

Prevent DataGrid ActiveX Control from running in Internet Explorer

You can disable attempts to instantiate a COM object in Internet Explorer by setting the kill bit for the control in the registry.

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

For detailed steps that you can use to prevent an ActiveX control from running in Internet Explorer, see Microsoft Knowledge Base Article 240797.

Follow these steps in this article to create a Compatibility Flags value in the registry to prevent a COM object from being instantiated in Internet Explorer.
1. Replace {cde57a43-8b86-11d0-b3c6-00a0c90aea82} below with the Class Identifiers found in this section.
2. To set the kill bit for a CLSID with a value of {cde57a43-8b86-11d0-b3c6-00a0c90aea82}, paste the following text in a text editor such as Notepad. Then, save the file by using the .reg file name extension.
  
  Windows Registry Editor Version 5.00
```
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{cde57a43-8b86-11d0-b3c6-00a0c90aea82}]
"Compatibility Flags"=dword:00000400
```
3. You can apply this .reg file to individual systems by double-clicking it. You can also apply it across domains by using Group Policy.
For more information about Group Policy, visit the following Microsoft Web sites:
Note You must restart Internet Explorer for your changes to take effect.

Impact of workaround. Web sites that require the DataGrid ActiveX Control may no longer function correctly.

How to undo the workaround.

Paste the following text in a text editor such as Notepad. Then, save the file by using the .reg file name extension.

Windows Registry Editor Version 5.00
```
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{cde57a43-8b86-11d0-b3c6-00a0c90aea82}]
"Compatibility Flags"=-
```
You can apply this .reg file to individual systems by double-clicking it. You can also apply it across domains by using Group Policy. For more information about Group Policy, visit the following Microsoft Web sites:
Note You must restart Internet Explorer for your changes to take effect.

FAQ for DataGrid Control Memory Corruption Vulnerability - CVE-2008-4252

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. 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?
When the ActiveX control is used in Internet Explorer, the control may corrupt the system state in such a way that an attacker could run arbitrary code.

What might an attacker use the vulnerability to do?
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?
An attacker could exploit the vulnerability by hosting a specially crafted Web site that is designed to invoke the ActiveX control through Internet Explorer. This can also include compromised Web sites and Web sites that accept or host user-provided content or advertisements. These Web sites could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or in an Instant Messenger request that takes users to the attacker's Web site. It could also be possible to display specially crafted Web content by using banner advertisements or by using other methods to deliver Web content to affected systems.

What systems are primarily at risk from the vulnerability?
This vulnerability requires that a user be logged on and visit a Web site for any malicious action to occur. Therefore, any systems where Internet Explorer is used frequently, such as workstations or terminal servers, are at the most risk from this vulnerability. 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.

I am running Internet Explorer for Windows Server 2003 or Windows Server 2008. Does this mitigate this vulnerability?
Yes. By default, Internet Explorer on Windows Server 2003 and Windows Server 2008 runs in a restricted mode that is known as Enhanced Security Configuration. Enhanced Security Configuration is a group of preconfigured settings in Internet Explorer that can reduce the likelihood of a user or administrator downloading and running specially crafted Web content on a server. This is a mitigating factor for Web sites that you have not added to the Internet Explorer Trusted sites zone. See also Managing Internet Explorer Enhanced Security Configuration.

What is the ActiveX opt-in feature in Windows Internet Explorer 7?
Windows Internet Explorer 7 includes an ActiveX opt-in feature, which means that nearly all pre-installed ActiveX controls are off by default. Users are prompted by the Information Bar before they can instantiate a previously installed ActiveX control that has not yet been used on the Internet. This enables a user to permit or deny access on a control-by-control basis. For more information about this and other new features, see the Windows Internet Explorer 7 features page.

What does the update do?
The update removes the vulnerability by handling errors for improperly initialized objects within the ActiveX Control.

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.

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.

FlexGrid Control Memory Corruption Vulnerability - CVE-2008-4253

A remote code execution vulnerability exists in the FlexGrid ActiveX Control for Visual Basic 6. An attacker could exploit the vulnerability by constructing a specially crafted Web page. When a user views the Web page, the vulnerability could allow remote code execution. An attacker who successfully exploited this vulnerability could gain the same user rights as the logged-on user.

To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2008-4253.

Mitigating Factors for FlexGrid Control Memory Corruption Vulnerability - CVE-2008-4253

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, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker’s Web site.
By default, Internet Explorer on Windows Server 2003 and Windows Server 2008 runs in a restricted mode that is known as Enhanced Security Configuration. This mode sets the security level for the Internet zone to High. This is a mitigating factor for Web sites that you have not added to the Internet Explorer Trusted sites zone. See the FAQ subsection of this vulnerability section for more information about Internet Explorer Enhanced Security Configuration.
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.
By default, all supported versions of Microsoft Outlook and Microsoft Outlook Express open HTML e-mail messages in the Restricted sites zone. The Restricted sites zone helps mitigate attacks that could try to exploit this vulnerability by preventing Active Scripting and ActiveX controls from being used when reading HTML e-mail messages. However, if a user clicks a link in an e-mail message, the user could still be vulnerable to exploitation of this vulnerability through the Web-based attack scenario.

Workarounds for FlexGrid Control Memory Corruption Vulnerability - CVE-2008-4253

Prevent FlexGrid ActiveX Control from running in Internet Explorer

You can disable attempts to instantiate a COM object in Internet Explorer by setting the kill bit for the control in the registry.

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

For detailed steps that you can use to prevent an ActiveX control from running in Internet Explorer, see Microsoft Knowledge Base Article 240797.

Follow these steps in this article to create a Compatibility Flags value in the registry to prevent a COM object from being instantiated in Internet Explorer.
1. Replace {6262d3a0-531b-11cf-91f6-c2863c385e30} below with the Class Identifiers found in this section.
2. To set the kill bit for a CLSID with a value of {6262d3a0-531b-11cf-91f6-c2863c385e30}, paste the following text in a text editor such as Notepad. Then, save the file by using the .reg file name extension.
  
  Windows Registry Editor Version 5.00
```
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{6262d3a0-531b-11cf-91f6-c2863c385e30}]
"Compatibility Flags"=dword:00000400
```
3. You can apply this .reg file to individual systems by double-clicking it. You can also apply it across domains by using Group Policy.
For more information about Group Policy, visit the following Microsoft Web sites:
Note You must restart Internet Explorer for your changes to take effect.

Impact of workaround. Web sites that require the FlexGrid ActiveX Control may no longer function correctly.

How to undo the workaround.

Paste the following text in a text editor such as Notepad. Then, save the file by using the .reg file name extension.

Windows Registry Editor Version 5.00
```
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{6262d3a0-531b-11cf-91f6-c2863c385e30}]
"Compatibility Flags"=-
```
You can apply this .reg file to individual systems by double-clicking it. You can also apply it across domains by using Group Policy. For more information about Group Policy, visit the following Microsoft Web sites:
Note You must restart Internet Explorer for your changes to take effect.

FAQ for FlexGrid Control Memory Corruption Vulnerability - CVE-2008-4253

What causes the vulnerability?
When the ActiveX control is used in Internet Explorer, the control may corrupt the system state in such a way that an attacker could run arbitrary code.

What does the update do?
The update removes the vulnerability by handling errors for improperly initialized objects within the ActiveX control.

Hierarchical FlexGrid Control Memory Corruption Vulnerability - CVE-2008-4254

A remote code execution vulnerability exists in the Hierarchical FlexGrid ActiveX Control for Visual Basic 6. An attacker could exploit the vulnerability by constructing a specially crafted Web page. When a user views the Web page, the vulnerability could allow remote code execution. An attacker who successfully exploited this vulnerability could gain the same user rights as the logged-on user.

To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2008-4254.

Mitigating Factors for Hierarchical FlexGrid Control Memory Corruption Vulnerability - CVE-2008-4254

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, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker’s Web site.
By default, Internet Explorer on Windows Server 2003 and Windows Server 2008 runs in a restricted mode that is known as Enhanced Security Configuration. This mode sets the security level for the Internet zone to High. This is a mitigating factor for Web sites that you have not added to the Internet Explorer Trusted sites zone. See the FAQ subsection of this vulnerability section for more information about Internet Explorer Enhanced Security Configuration.
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.
By default, all supported versions of Microsoft Outlook and Microsoft Outlook Express open HTML e-mail messages in the Restricted sites zone. The Restricted sites zone helps mitigate attacks that could try to exploit this vulnerability by preventing Active Scripting and ActiveX controls from being used when reading HTML e-mail messages. However, if a user clicks a link in an e-mail message, the user could still be vulnerable to exploitation of this vulnerability through the Web-based attack scenario.

Workarounds for Hierarchical FlexGrid Control Memory Corruption Vulnerability - CVE-2008-4254

Prevent Hierarchical FlexGrid ActiveX Control from running in Internet Explorer

You can disable attempts to instantiate a COM object in Internet Explorer by setting the kill bit for the control in the registry.

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

For detailed steps that you can use to prevent an ActiveX control from running in Internet Explorer, see Microsoft Knowledge Base Article 240797.

Follow these steps in this article to create a Compatibility Flags value in the registry to prevent a COM object from being instantiated in Internet Explorer.
1. Replace {0ECD9B64-23AA-11d0-B351-00A0C9055D8E} below with the Class Identifiers found in this section.
2. To set the kill bit for a CLSID with a value of {0ECD9B64-23AA-11d0-B351-00A0C9055D8E}, paste the following text in a text editor such as Notepad. Then, save the file by using the .reg file name extension. Windows Registry Editor Version 5.00
```
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{0ECD9B64-23AA-11d0-B351-00A0C9055D8E}]
"Compatibility Flags"=dword:00000400
```
3. You can apply this .reg file to individual systems by double-clicking it. You can also apply it across domains by using Group Policy.
For more information about Group Policy, visit the following Microsoft Web sites:
Note You must restart Internet Explorer for your changes to take effect.

Impact of workaround. Web sites that require the Hierarchical FlexGrid ActiveX Control may no longer function correctly.

How to undo the workaround.

Paste the following text in a text editor such as Notepad. Then, save the file by using the .reg file name extension.

Windows Registry Editor Version 5.00
```
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{0ECD9B64-23AA-11d0-B351-00A0C9055D8E}]
"Compatibility Flags"=-
```
You can apply this .reg file to individual systems by double-clicking it. You can also apply it across domains by using Group Policy. For more information about Group Policy, visit the following Microsoft Web sites:
Note You must restart Internet Explorer for your changes to take effect.

FAQ for Hierarchical FlexGrid Control Memory Corruption Vulnerability - CVE-2008-4254

What causes the vulnerability?
When the ActiveX control is used in Internet Explorer, the control may corrupt the system state in such a way that an attacker could run arbitrary code.

What does the update do?
The update removes the vulnerability by handling errors for improperly initialized objects within the ActiveX control.

Windows Common AVI Parsing Overflow Vulnerability - CVE-2008-4255

A remote code execution vulnerability exists in the Windows Common ActiveX Control for Visual Basic 6. An attacker could exploit the vulnerability by constructing a specially crafted Web page. When a user views the Web page, the vulnerability could allow remote code execution. An attacker who successfully exploited this vulnerability could gain the same user rights as the logged-on user.

To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2008-4255.

Mitigating Factors for Windows Common AVI Parsing Overflow Vulnerability - CVE-2008-4255

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, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker’s Web site.
By default, Internet Explorer on Windows Server 2003 and Windows Server 2008 runs in a restricted mode that is known as Enhanced Security Configuration. This mode sets the security level for the Internet zone to High. This is a mitigating factor for Web sites that you have not added to the Internet Explorer Trusted sites zone. See the FAQ subsection of this vulnerability section for more information about Internet Explorer Enhanced Security Configuration.
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.
By default, all supported versions of Microsoft Outlook and Microsoft Outlook Express open HTML e-mail messages in the Restricted sites zone. The Restricted sites zone helps mitigate attacks that could try to exploit this vulnerability by preventing Active Scripting and ActiveX controls from being used when reading HTML e-mail messages. However, if a user clicks a link in an e-mail message, the user could still be vulnerable to exploitation of this vulnerability through the Web-based attack scenario.

Workarounds for Windows Common AVI Parsing Overflow Vulnerability - CVE-2008-4255

Prevent Windows Common AVI ActiveX Control from running in Internet Explorer

You can disable attempts to instantiate a COM object in Internet Explorer by setting the kill bit for the control in the registry. For information on how to prevent a control from running in Internet Explorer, see Microsoft Knowledge Base Article 240797. This article also shows you how to create a Compatibility Flags value in the registry to prevent a COM object from being instantiated in Internet Explorer.

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To prevent the Windows Common AVI ActiveX Control from running in Internet Explorer, do the following to set the kill bits for the control in the registry:

Paste the following text in a text editor such as Notepad. Then, save the file by using the .reg file name extension.

Windows Registry Editor Version 5.00
```
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{B09DE715-87C1-11d1-8BE3-0000F8754DA1}]
"Compatibility Flags"=dword:00000400

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{1E216240-1B7D-11CF-9D53-00AA003C9CB6}]
"Compatibility Flags"=dword:00000400
```
Apply this .reg file to individual systems by double-clicking it.

You can also apply it across domains by using Group Policy. For more information about Group Policy, visit the following Microsoft Web sites:
Note You must restart Internet Explorer for your changes to take effect.

Impact of workaround. Web sites that require the Windows Common AVI ActiveX Control may no longer function correctly.

How to undo the workaround.

Paste the following text in a text editor such as Notepad. Then, save the file by using the .reg file name extension.

Windows Registry Editor Version 5.00
```
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{B09DE715-87C1-11d1-8BE3-0000F8754DA1}]
"Compatibility Flags"=-

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{1E216240-1B7D-11CF-9D53-00AA003C9CB6}]
"Compatibility Flags"=-
```
You can apply this .reg file to individual systems by double-clicking it. You can also apply it across domains by using Group Policy. For more information about Group Policy, visit the following Microsoft Web sites:
Note You must restart Internet Explorer for your changes to take effect.

FAQ for Windows Common AVI Parsing Overflow Vulnerability - CVE-2008-4255

What causes the vulnerability?
The vulnerability is caused by an allocation error when parsing a specially crafted AVI file. The error may corrupt system memory in such a way that an attacker could run arbitrary code.

What does the update do?
The update removes the vulnerability by validating stream lengths of AVI files parsed by the ActiveX control.

Charts Control Memory Corruption Vulnerability - CVE-2008-4256

A remote code execution vulnerability exists in the Charts ActiveX Control for Visual Basic 6. An attacker could exploit the vulnerability by constructing a specially crafted Web page. When a user views the Web page, the vulnerability could allow remote code execution. An attacker who successfully exploited this vulnerability could gain the same user rights as the logged-on user.

To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2008-4256.

Mitigating Factors for Charts Control Memory Corruption Vulnerability - CVE-2008-4256

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, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker’s Web site.
By default, Internet Explorer on Windows Server 2003 and Windows Server 2008 runs in a restricted mode that is known as Enhanced Security Configuration. This mode sets the security level for the Internet zone to High. This is a mitigating factor for Web sites that you have not added to the Internet Explorer Trusted sites zone. See the FAQ subsection of this vulnerability section for more information about Internet Explorer Enhanced Security Configuration.
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.
By default, all supported versions of Microsoft Outlook and Microsoft Outlook Express open HTML e-mail messages in the Restricted sites zone. The Restricted sites zone helps mitigate attacks that could try to exploit this vulnerability by preventing Active Scripting and ActiveX controls from being used when reading HTML e-mail messages. However, if a user clicks a link in an e-mail message, the user could still be vulnerable to exploitation of this vulnerability through the Web-based attack scenario.

Workarounds for Charts Control Memory Corruption Vulnerability - CVE-2008-4256

Prevent Charts ActiveX Control from running in Internet Explorer

You can disable attempts to instantiate a COM object in Internet Explorer by setting the kill bit for the control in the registry.

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

For detailed steps that you can use to prevent an ActiveX control from running in Internet Explorer, see Microsoft Knowledge Base Article 240797.

Follow these steps in this article to create a Compatibility Flags value in the registry to prevent a COM object from being instantiated in Internet Explorer.
1. Replace {3A2B370C-BA0A-11d1-B137-0000F8753F5D} below with the Class Identifiers found in this section.
2. To set the kill bit for a CLSID with a value of {3A2B370C-BA0A-11d1-B137-0000F8753F5D}, paste the following text in a text editor such as Notepad. Then, save the file by using the .reg file name extension. Windows Registry Editor Version 5.00
```
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{3A2B370C-BA0A-11d1-B137-0000F8753F5D}]
"Compatibility Flags"=dword:00000400
```
3. You can apply this .reg file to individual systems by double-clicking it. You can also apply it across domains by using Group Policy.
For more information about Group Policy, visit the following Microsoft Web sites:
Note You must restart Internet Explorer for your changes to take effect.

Impact of workaround. Web sites that require the Charts ActiveX Control may no longer function correctly.

How to undo the workaround.

Paste the following text in a text editor such as Notepad. Then, save the file by using the .reg file name extension.

Windows Registry Editor Version 5.00
```
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{3A2B370C-BA0A-11d1-B137-0000F8753F5D}]
"Compatibility Flags"=-
```
You can apply this .reg file to individual systems by double-clicking it. You can also apply it across domains by using Group Policy. For more information about Group Policy, visit the following Microsoft Web sites:
Note You must restart Internet Explorer for your changes to take effect.

FAQ for Charts Control Memory Corruption Vulnerability - CVE-2008-4256

What causes the vulnerability?
When the ActiveX control is used in Internet Explorer, the control may corrupt the system state in such a way that an attacker could run arbitrary code.

What does the update do?
The update removes the vulnerability by handing errors for improperly initialized objects within the ActiveX control.

Masked Edit Control Memory Corruption Vulnerability - CVE-2008-3704

A remote code execution vulnerability exists in the Masked Edit ActiveX Control for Visual Basic 6. An attacker could exploit the vulnerability by constructing a specially crafted Web page. When a user views the Web page, the vulnerability could allow remote code execution. An attacker who successfully exploited this vulnerability could gain the same user rights as the logged-on user.

To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2008-3704.

Mitigating Factors for Masked Edit Control Memory Corruption Vulnerability - CVE-2008-3704

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, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker’s Web site.
By default, Internet Explorer on Windows Server 2003 and Windows Server 2008 runs in a restricted mode that is known as Enhanced Security Configuration. This mode sets the security level for the Internet zone to High. This is a mitigating factor for Web sites that you have not added to the Internet Explorer Trusted sites zone. See the FAQ subsection of this vulnerability section for more information about Internet Explorer Enhanced Security Configuration.
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.
By default, all supported versions of Microsoft Outlook and Microsoft Outlook Express open HTML e-mail messages in the Restricted sites zone. The Restricted sites zone helps mitigate attacks that could try to exploit this vulnerability by preventing Active Scripting and ActiveX controls from being used when reading HTML e-mail messages. However, if a user clicks a link in an e-mail message, the user could still be vulnerable to exploitation of this vulnerability through the Web-based attack scenario.

Workarounds for Masked Edit Control Memory Corruption Vulnerability - CVE-2008-3704

Prevent Masked EditActiveX Control from running in Internet Explorer

You can disable attempts to instantiate a COM object in Internet Explorer by setting the kill bit for the control in the registry.

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

For detailed steps that you can use to prevent an ActiveX control from running in Internet Explorer, see Microsoft Knowledge Base Article 240797.

Follow these steps in this article to create a Compatibility Flags value in the registry to prevent a COM object from being instantiated in Internet Explorer.
1. Replace {C932BA85-4374-101B-A56C-00AA003668DC} below with the Class Identifiers found in this section.
2. To set the kill bit for a CLSID with a value of {C932BA85-4374-101B-A56C-00AA003668DC}, paste the following text in a text editor such as Notepad. Then, save the file by using the .reg file name extension. Windows Registry Editor Version 5.00
```
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{C932BA85-4374-101B-A56C-00AA003668DC}]
"Compatibility Flags"=dword:00000400
```
3. You can apply this .reg file to individual systems by double-clicking it. You can also apply it across domains by using Group Policy.
For more information about Group Policy, visit the following Microsoft Web sites:
Note You must restart Internet Explorer for your changes to take effect.

Impact of workaround. Web sites that require the Charts ActiveX Control may no longer function correctly.

How to undo the workaround.

Paste the following text in a text editor such as Notepad. Then, save the file by using the .reg file name extension.

Windows Registry Editor Version 5.00
```
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{C932BA85-4374-101B-A56C-00AA003668DC}]
"Compatibility Flags"=-
```
You can apply this .reg file to individual systems by double-clicking it. You can also apply it across domains by using Group Policy. For more information about Group Policy, visit the following Microsoft Web sites:
Note You must restart Internet Explorer for your changes to take effect.

FAQ for Masked Edit Control Memory Corruption Vulnerability - CVE-2008-3704

What causes the vulnerability?
The ActiveX control does not correctly handle property values, which causes a buffer overrun when used in Internet Explorer that could allow an attacker to run arbitrary code.

What does the update do?
The update removes the vulnerability by validating property values with boundary checks when the ActiveX control is used in Internet Explorer.

When this security bulletin was issued, had this vulnerability been publicly disclosed?
Yes. This vulnerability had been publicly disclosed when this security bulletin was originally issued. It has been assigned the Common Vulnerability and Exposure number CVE-2008-3704.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
Yes. Microsoft is aware of limited, targeted attacks attempting to exploit the vulnerability.

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 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 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), and the Extended Security Update Inventory Tool. 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.

The following table provides the MBSA detection summary for this security update.

Software	MBSA 2.1
Microsoft Visual Basic 6.0 Runtime Extended Files	No
Microsoft Visual Studio .NET 2002 Service Pack 1	No
Microsoft Visual Studio .NET 2003 Service Pack 1	No
Microsoft Visual FoxPro 8.0 Service Pack 1	No
Microsoft Visual FoxPro 9.0 Service Pack 1	No
Microsoft Visual FoxPro 9.0 Service Pack 2	No
Microsoft Office FrontPage 2002 Service Pack 3	Yes
Microsoft Office Project 2003 Service Pack 3	Yes
Microsoft Office Project 2007	Yes
Microsoft Office Project 2007 Service Pack 1	Yes

For more information about MBSA 2.1, see MBSA 2.1 Frequently Asked Questions.

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

Software	SMS 2.0	SMS 2003 with SUSFP	SMS 2003 with ITMU	SCCM 2007
Microsoft Visual Basic 6.0 Runtime Extended Files	No	Yes	No	No
Microsoft Visual Studio .NET 2002 Service Pack 1	Yes	Yes	No	No
Microsoft Visual Studio .NET 2003 Service Pack 1	Yes	Yes	No	No
Microsoft Visual FoxPro 8.0 Service Pack 1	Yes	Yes	No	No
Microsoft Visual FoxPro 9.0 Service Pack 1	No	No	No	No
Microsoft Visual FoxPro 9.0 Service Pack 2	No	No	No	No
Microsoft Office FrontPage 2002 Service Pack 3	Yes	Yes	Yes	Yes
Microsoft Office Project 2003 Service Pack 3	Yes	Yes	Yes	Yes
Microsoft Office Project 2007	No	No	Yes	Yes
Microsoft Office Project 2007 Service Pack 1	No	No	Yes	Yes

For SMS 2.0 and SMS 2003, the SMS SUS Feature Pack (SUSFP), which includes 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. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications. For more information about the Office Inventory Tool and other scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003.

System Center Configuration Manager (SCCM) 2007 uses WSUS 3.0 for detection of updates. For more information about SCCM 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.

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

The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Microsoft Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.

Security Update Deployment

Affected Software

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

Microsoft Visual Basic 6.0 Service Pack 6

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 may be included in a future update rollup
Deployment
Installing without user intervention	VB60SP6-KB926857-x86-enu /qn
Installing without restarting	VB60SP6-KB926857-x86-enu /norestart
Update log file	Not applicable
Further information	See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?	This update requires a restart
HotPatching	Not applicable
Removal Information	This update cannot be removed.
File Information	See Microsoft Knowledge Base Article 932349
Registry Key Verification	HKEY_LOCAL_MACHINE\Software\Microsoft\Updates\VB6\KB926857\ "Installed" = dword:1

Deployment Information

Installing the Update

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.

Switch	Description
/? or /h or /help	Display usage dialog box.
Setup Mode
/q[n	b	r	f]	Sets user interface level\ n - No UI\ b - Basic UI\ r - Reduced UI\ f - Full UI
/quiet	Same as /q
/passive	Same as /qb
Restart Options
/norestart	Do not restart after the installation is complete
/promptrestart	Prompts the user for restart if necessary
/forcerestart	Restart the computer after installation if necessary (e.g. if a file is locked or in use)
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

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 this Microsoft MSDN article.

Removing the Update

This update cannot be removed.

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

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.
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 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.
1. 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 Visual Studio .NET 2002 Service Pack 1

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	VS7.0sp1-KB958392-X86-intl /q
Installing without restarting	VS7.0sp1-KB958392-X86-intl /norestart
Update log file	VS7.0SP1-KB958392-X86-intl-msi.0.log\ VS7.0SP1-KB958392-X86-intl-wrapper.log
Further information	For detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance.
Restart Requirement
Restart required?	This update requires a restart.
Hotpatching	Not applicable
Removal Information	Use Add or Remove Programs tool in Control Panel.
File Information	See Microsoft Knowledge Base Article 932349
Registry Key Verification	HKEY_LOCAL_MACHINE\Software\Microsoft\Updates\Visual Studio\7.0\M958392\ "Installed" = dword:1

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

Switch	Description
/? or /h or /help	Display usage dialog box.
Setup Mode
/q[n	b	r	f]	Sets user interface level\ n - No UI\ b - Basic UI\ r - Reduced UI\ f - Full UI
/quiet	Same as /q
/passive	Same as /qb
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 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	Restart the computer after installation if necessary (e.g. if a file is locked or in use)
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.

Removing the Update

To remove this security update, use the Add or Remove Programs tool 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 section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
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.
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 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.
1. 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 Visual Studio .NET 2003 Service Pack 1

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	VS7.1sp1-KB958393-X86 /q
Installing without restarting	VS7.1sp1-KB958393-X86 /norestart
Update log file	VS7.1SP1-KB958393-X86-intl-msi.0.log\ VS7.1SP1-KB958393-X86-intl-wrapper.log
Further information	For detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance.
Restart Requirement
Restart required?	This update requires a restart.
Hotpatching	Not applicable
Removal Information	Use Add or Remove Programs tool in Control Panel.
File Information	See Microsoft Knowledge Base Article 932349
Registry Key Verification	HKEY_LOCAL_MACHINE\Software\Microsoft\Updates\Visual Studio\7.1\M958393\ "Installed" = dword:1

Deployment Information

Installing the Update

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:

This security update supports the following setup switches.

Switch	Description
/? or /h or /help	Display usage dialog box.
Setup Mode
/q[n	b	r	f]	Sets user interface level\ n - No UI\ b - Basic UI\ r - Reduced UI\ f - Full UI
/quiet	Same as /q
/passive	Same as /qb
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 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	Restart the computer after installation if necessary (e.g. if a file is locked or in use)
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.

Removing the Update

To remove this security update, use the Add or Remove Programs tool 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 section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
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.
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 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.
1. 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 Visual FoxPro 8.0 Service Pack 1

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	Microsoft Visual FoxPro 8.0 Service Pack 1:\ VFP8.0sp1-KB958369-X86-enu /qn
Installing without restarting	Microsoft Visual FoxPro 8.0 Service Pack 1:\ VFP8.0sp1-KB958369-X86-enu /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 requires a restart.
Hotpatching	Not applicable
Removal Information	This update cannot be removed.
File Information	See Microsoft Knowledge Base Article 932349
Registry Key Verification	Microsoft Visual FoxPro 8.0 Service Pack 1:\ SOFTWARE\Microsoft\Updates\Visual Studio\8.0\M958369\ "Installed" = dword:1

Deployment Information

Installing the Update

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.

Switch	Description
/? or /h or /help	Display usage dialog box.
Setup Mode
/q[n	b	r	f]	Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
f - Full UI
/quiet	Same as /q
/passive	Same as /qb
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 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	Restart the computer after installation if necessary (e.g. if a file is locked or in use)
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.

Removing the Update

This update cannot be removed.

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

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.
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 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.
1. 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 Visual FoxPro 9.0 Service Pack 1 and Microsoft Visual FoxPro 9.0 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 Visual FoxPro 9.0 Service Pack 3
Deployment
Installing without user intervention	Microsoft Visual FoxPro 9.0 Service Pack 1:\ VFP9.0sp1-KB958370-X86-enu /qn\ \ Microsoft Visual FoxPro 9.0 Service Pack 2:\ VFP9.0sp2-KB958371-X86-enu /qn
Installing without restarting	Microsoft Visual FoxPro 9.0 Service Pack 1:\ VFP9.0sp1-KB958370-X86-enu /norestart\ \ Microsoft Visual FoxPro 9.0 Service Pack 2:\ VFP9.0sp2-KB958371-X86-enu /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 requires a restart.
Hotpatching	Not applicable
Removal Information	Use Add or Remove Programs tool in Control Panel.
File Information	See Microsoft Knowledge Base Article 932349
Registry Key Verification	Microsoft Visual FoxPro 9.0 Service Pack 1:\ SOFTWARE\Microsoft\Updates\Visual Studio\9.0\M958370\ "Installed" = dword:1\ \ Microsoft Visual FoxPro 9.0 Service Pack 2:\ SOFTWARE\Microsoft\Updates\Visual Studio\9.0\M955371\ "Installed" = dword:1

Deployment Information

Installing the Update

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.

Switch	Description
/? or /h or /help	Display usage dialog box.

Setup Mode
/q[n	b	r	f]	Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
f - Full UI
/quiet	Same as /q
/passive	Same as /qb
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 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	Restart the computer after installation if necessary (e.g. if a file is locked or in use)
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.

Removing the Update

To remove this security update, use the Add or Remove Programs tool 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 section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
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.
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 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.
1. 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 Office FrontPage 2002 Service Pack 3 for Chinese Simplified (China), Chinese Pan (Hong Kong), Chinese Traditional (Taiwan), and Korean

Note This update only applies to FrontPage 2002 Service Pack 3 versions in Chinese Simplified (China), Chinese Pan (Hong Kong), Chinese Traditional (Taiwan), and Korean.

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	For Chinese Simplified (China):\ OfficeXP-KB957797-FullFile-chs /q:a\ \ For Chinese Pan (Hong Kong):\ OfficeXP-KB957797-FullFile-zhh /q:a\ \ For Chinese Traditional (Taiwan):\ OfficeXP-kb957797-FullFile-cht /q:a\ \ For Korean:\ OfficeXP-KB957797-FullFile-kor /q:a
Installing without restarting	For Chinese Simplified (China):\ OfficeXP-KB957797-FullFile-chs /r:n\ \ For Chinese Pan (Hong Kong):\ OfficeXP-KB957797-FullFile-zhh /r:n\ \ For Chinese Traditional (Taiwan):\ OfficeXP-KB957797-FullFile-cht /r:n\ \ For Korean:\ OfficeXP-KB957797-FullFile-kor /r:n
Update log file	Not applicable
Further information	For 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.
Hotpatching	Not applicable
Removal Information	This update cannot be removed.
File Information	See Microsoft Knowledge Base Article 932349
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:

Product	Feature
FrontPage 2002 SP3	FPClientNonBootFiles, ProductNonBootFiles

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

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.

Removing the Update

This update cannot be removed.

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 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.
1. 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 Office Project 2003 Service Pack 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	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	For Microsoft Office Project 2003 Service Pack 3:\ Office2003-KB949045-FullFile-enu /q:a
Installing without restarting	For Microsoft Office Project 2003 Service Pack 3:\ Office2003-KB949045-FullFile-enu /r:n
Update log file	Not applicable
Further information	For 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.
Hotpatching	Not applicable
Removal Information	This update cannot be removed.
File Information	See Microsoft Knowledge Base Article 932349
Registry Key Verification	Not applicable

Office Features

Product	Feature
Project 2003 SP3	PROJECTFiles

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

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.

Removing the Update

This update cannot be removed.

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 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.
1. 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 Office Project 2007 and Microsoft Office Project 2007 Service Pack 1

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	For Microsoft Office Project 2007:\ Project2007-KB949046-FullFile-x86-glb /passive\ \ For Microsoft Office Project 2007 Service Pack 1:\ Project2007-KB949046-FullFile-x86-glb /passive\
Installing without restarting	For Microsoft Office Project 2007:\ Project2007-KB949046-FullFile-x86-glb /norestart\ \ For Microsoft Office Project 2007 Service Pack 1:\ Project2007-KB949046-FullFile-x86-glb /norestart
Update log file	Not applicable
Further information	For 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.
Hotpatching	Not applicable
Removal Information	Use Add or Remove Programs tool in Control Panel.
File Information	See Microsoft Knowledge Base Article 932349
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:

Product	Feature
Project 2007	PROJECTFiles

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

Switch	Description
/? or /help	Displays usage dialog.
/passive	Specifies passive mode. Requires no user interaction; users see basic progress dialogs but cannot cancel.
/quiet	Specifies quiet mode, or suppresses prompts, when files are being extracted.
/norestart	Suppresses restarting the system if the update requires a restart.
/forcerestart	Automatically restarts the system after applying the update, regardless of whether the update requires the restart.
/extract	Extracts the files without installing them. You are prompted for a target folder.
/extract:<path>	Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file.
/lang:<LCID>	Forces the use of a specific language, when the update package supports that language.
/log:<log file>	Enables logging, by both Vnox and Installer, during the update installation.

Removing the Update

This update cannot be removed.

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

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

ADLab of VenusTech for reporting the DataGrid Control Memory Corruption Vulnerability (CVE-2008-4252)
ADLab of VenusTech for reporting the FlexGrid Control Memory Corruption Vulnerability (CVE-2008-4253)
ADLab of VenusTech for reporting the Hierarchical FlexGrid Control Memory Corruption Vulnerability (CVE-2008-4254)
Jason Medeiros of Affiliated Computer Services for reporting the Hierarchical FlexGrid Control Memory Corruption Vulnerability (CVE-2008-4254)
Carsten Eiram of Secunia Research for reporting the Hierarchical FlexGrid Control Memory Corruption Vulnerability (CVE-2008-4254)
Mark Dowd, working with McAfee Avert Labs, for reporting the Windows Common AVI Parsing Overflow Vulnerability (CVE-2008-4255)
Brett Moore of Insomnia Security for reporting the Windows Common AVI Parsing Overflow Vulnerability (CVE-2008-4255)
CHkr_D591, working with TippingPoint and the Zero Day Initiative, for reporting the Windows Common AVI Parsing Overflow Vulnerability (CVE-2008-4255)
Michal Bucko, working with CERT/CC, for reporting the Charts Control Memory Corruption Vulnerability (CVE-2008-4256)
Symantec’s Security Intelligence Analysis Team for working with us on the Masked Edit Control Memory Corruption Vulnerability (CVE-2008-3704)

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 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 (December 9, 2008): Bulletin published.
V1.1 (December 15, 2008): Added an entry in the section, Frequently asked questions (FAQ) related to this security update, announcing that Microsoft has released a cumulative update for Microsoft Visual Basic 6.0 Service Pack 6 (KB957924) that includes the update for Microsoft Visual Basic 6.0 Runtime Extended Files (KB926857) provided in this bulletin. This is an informational change only. There were no changes to the security update binaries in this bulletin.
V1.2 (February 11, 2009): Clarified the class IDs for two ActiveX controls. First, listed a second class ID in the workaround, "Prevent Windows Common AVI ActiveX Control from running in Internet Explorer," for CVE-2008-4255. Second, listed in the section, Frequently asked questions (FAQ) related to this security update, the class ID for the Winsock Control for which the kill bit is being set as a security-related change to functionality in this update. This is an informational change only. There were no changes to the security update files in this bulletin.

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

Microsoft Security Bulletin MS08-070 - Critical

Vulnerabilities in Visual Basic 6.0 Runtime Extended Files (ActiveX Controls) Could Allow Remote Code Execution (932349)

General Information

Executive Summary

Affected and Non-Affected Software

Frequently Asked Questions (FAQ) Related to This Security Update

Vulnerability Information

Severity Ratings and Vulnerability Identifiers

DataGrid Control Memory Corruption Vulnerability - CVE-2008-4252

Mitigating Factors for DataGrid Control Memory Corruption Vulnerability - CVE-2008-4252

Workarounds for DataGrid Control Memory Corruption Vulnerability - CVE-2008-4252

FAQ for DataGrid Control Memory Corruption Vulnerability - CVE-2008-4252

FlexGrid Control Memory Corruption Vulnerability - CVE-2008-4253

Mitigating Factors for FlexGrid Control Memory Corruption Vulnerability - CVE-2008-4253

Workarounds for FlexGrid Control Memory Corruption Vulnerability - CVE-2008-4253

FAQ for FlexGrid Control Memory Corruption Vulnerability - CVE-2008-4253

Hierarchical FlexGrid Control Memory Corruption Vulnerability - CVE-2008-4254

Mitigating Factors for Hierarchical FlexGrid Control Memory Corruption Vulnerability - CVE-2008-4254

Workarounds for Hierarchical FlexGrid Control Memory Corruption Vulnerability - CVE-2008-4254

FAQ for Hierarchical FlexGrid Control Memory Corruption Vulnerability - CVE-2008-4254

Windows Common AVI Parsing Overflow Vulnerability - CVE-2008-4255

Mitigating Factors for Windows Common AVI Parsing Overflow Vulnerability - CVE-2008-4255

Workarounds for Windows Common AVI Parsing Overflow Vulnerability - CVE-2008-4255

FAQ for Windows Common AVI Parsing Overflow Vulnerability - CVE-2008-4255

Charts Control Memory Corruption Vulnerability - CVE-2008-4256

Mitigating Factors for Charts Control Memory Corruption Vulnerability - CVE-2008-4256

Workarounds for Charts Control Memory Corruption Vulnerability - CVE-2008-4256

FAQ for Charts Control Memory Corruption Vulnerability - CVE-2008-4256

Masked Edit Control Memory Corruption Vulnerability - CVE-2008-3704

Mitigating Factors for Masked Edit Control Memory Corruption Vulnerability - CVE-2008-3704

Workarounds for Masked Edit Control Memory Corruption Vulnerability - CVE-2008-3704

FAQ for Masked Edit Control Memory Corruption Vulnerability - CVE-2008-3704

Update Information

Detection and Deployment Tools and Guidance

Security Update Deployment

Microsoft Visual Basic 6.0 Service Pack 6

Deployment Information

Microsoft Visual Studio .NET 2002 Service Pack 1

Deployment Information

Microsoft Visual Studio .NET 2003 Service Pack 1

Deployment Information

Microsoft Visual FoxPro 8.0 Service Pack 1

Deployment Information

Microsoft Visual FoxPro 9.0 Service Pack 1 and Microsoft Visual FoxPro 9.0 Service Pack 2

Deployment Information

Microsoft Office FrontPage 2002 Service Pack 3 for Chinese Simplified (China), Chinese Pan (Hong Kong), Chinese Traditional (Taiwan), and Korean

Office Features

Deployment Information

Microsoft Office Project 2003 Service Pack 3

Office Features

Deployment Information

Microsoft Office Project 2007 and Microsoft Office Project 2007 Service Pack 1

Office Features

Deployment Information

Other Information

Acknowledgments

Microsoft Active Protections Program (MAPP)

Support

Disclaimer

Revisions

Additional resources