Security Bulletin

Microsoft Security Bulletin MS07-040 - Critical

Vulnerabilities in .NET Framework Could Allow Remote Code Execution (931212)

Published: July 10, 2007 | Updated: May 07, 2009

Version: 4.0

General Information

Executive Summary

This update resolves three privately reported vulnerabilities. Two of these vulnerabilities could allow remote code execution on client systems with .NET Framework installed, and one could allow information disclosure on Web servers running ASP.NET. In all remote code execution cases, 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 addresses two vulnerabilities by modifying the way .NET Framework addresses buffer allocation. 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 931212 documents the currently known issues that customers may experience when they install this security update. The article also documents recommended solutions for these issues.

Affected and Non-Affected Software

In the following tables of affected and non-affected software, software versions that are not listed are past their support lifecycle. To determine the support lifecycle for your product and version, visit Microsoft Support Lifecycle.

Affected Software

Operating System Component Maximum Security Impact Aggregate Severity Rating Bulletins Replaced by This Update
Microsoft .NET Framework 1.0 Service Pack 3
Windows 2000 Service Pack 4 Microsoft .NET Framework 1.0
(KB928367)
Remote Code Execution Critical MS05-004
Windows XP Service Pack 2 and Windows XP Service Pack 3 Microsoft .NET Framework 1.0
(KB928367)
Remote Code Execution Critical MS05-004
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 Microsoft .NET Framework 1.0
(KB928367)
Remote Code Execution Critical MS05-004
Windows XP Tablet PC Edition 2005 and Windows XP Media Center Edition 2005 Microsoft .NET Framework 1.0
(KB930494)
Remote Code Execution Critical MS05-004
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 Microsoft .NET Framework 1.0
(KB928367)
Remote Code Execution Important MS05-004
Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems Microsoft .NET Framework 1.0
(KB928367)
Remote Code Execution Important MS05-004
Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 Microsoft .NET Framework 1.0
(KB928367)
Remote Code Execution Important MS05-004
Windows Vista and Windows Vista Service Pack 1 Microsoft .NET Framework 1.0
(KB928367)
Information Disclosure Important MS05-004
Windows Vista Service Pack 2 Microsoft .NET Framework 1.0
(KB928367)
Information Disclosure Important None
Windows Server 2008 and Windows Server 2008 Service Pack 2 Microsoft .NET Framework 1.0
(KB928367)
Information Disclosure Important None
Microsoft .NET Framework 1.1 Service Pack 1
Windows 2000 Service Pack 4 Microsoft .NET Framework 1.1
(KB928366)
Remote Code Execution Critical MS05-004
Windows XP Service Pack 2 and Windows XP Service Pack 3 Microsoft .NET Framework 1.1
(KB928366)
Remote Code Execution Critical MS05-004
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 Microsoft .NET Framework 1.1
(KB928366)
Remote Code Execution Critical MS05-004
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 Microsoft .NET Framework 1.1
(KB933854)
Remote Code Execution Important MS05-004
Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems Microsoft .NET Framework 1.1
(KB928366)
Remote Code Execution Important MS05-004
Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 Microsoft .NET Framework 1.1
(KB928366)
Remote Code Execution Important MS05-004
Windows Vista and Windows Vista Service Pack 1 Microsoft .NET Framework 1.1
(KB929729)
Information Disclosure Important MS05-004
Windows Vista Service Pack 2 Microsoft .NET Framework 1.1
(KB929729)
Information Disclosure Important None
Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1 Microsoft .NET Framework 1.1
(KB929729)
Information Disclosure Important MS05-004
Windows Vista x64 Edition Service Pack 2 Microsoft .NET Framework 1.1
(KB929729)
Information Disclosure Important None
Windows Server 2008 and Windows Server 2008 Service Pack 2 Microsoft .NET Framework 1.1
(KB929729)
Information Disclosure Important None
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2 Microsoft .NET Framework 1.1
(KB929729)
Information Disclosure Important None
Windows Server 2008 x64 Edition and Windows Server 2008 x64 Edition Service Pack 2 Microsoft .NET Framework 1.1
(KB929729)
Information Disclosure Important None
Microsoft .NET Framework 2.0
Windows 2000 Service Pack 4 Microsoft .NET Framework 2.0
(KB928365)
Remote Code Execution Critical MS06-033, MS06-056
Windows XP Service Pack 2 and Windows XP Service Pack 3 Microsoft .NET Framework 2.0
(KB928365)
Remote Code Execution Critical MS06-033, MS06-056
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 Microsoft .NET Framework 2.0
(KB928365)
Remote Code Execution Critical MS06-033, MS06-056
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 Microsoft .NET Framework 2.0
(KB928365)
Remote Code Execution Important MS06-033, MS06-056
Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems Microsoft .NET Framework 2.0
(KB928365)
Remote Code Execution Important MS06-033, MS06-056
Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 Microsoft .NET Framework 2.0
(KB928365)
Remote Code Execution Important MS06-033, MS06-056
Windows Vista Microsoft .NET Framework 2.0
(KB929916)
Information Disclosure Important None
Windows Vista x64 Edition Microsoft .NET Framework 2.0
(KB929916)
Information Disclosure Important None

Non-Affected Software

Operating System Component
Windows XP Service Pack 2 and Windows XP Service Pack 3 Microsoft .NET Framework 3.0, Microsoft .NET Framework 3.0 Service Pack 1, and Microsoft .NET Framework 3.5
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 Microsoft .NET Framework 3.0, Microsoft .NET Framework 3.0 Service Pack 1, and Microsoft .NET Framework 3.5
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 Microsoft .NET Framework 3.0, Microsoft .NET Framework 3.0 Service Pack 1, and Microsoft .NET Framework 3.5
Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 Microsoft .NET Framework 3.0, Microsoft .NET Framework 3.0 Service Pack 1, and Microsoft .NET Framework 3.5
Windows Vista Microsoft .NET Framework 3.0 and Microsoft .NET Framework 3.5
Windows Vista x64 Edition Microsoft .NET Framework 3.0 and Microsoft .NET Framework 3.5
Windows Vista Service Pack 1 and Windows Vista Service Pack 2 Microsoft .NET Framework 2.0 Service Pack 1, Microsoft .NET Framework 3.0 Service Pack 1, and Microsoft .NET Framework 3.5
Windows Vista x64 Edition Service Pack 1 and Windows Vista x64 Edition Service Pack 2 Microsoft .NET Framework 2.0 Service Pack 1, Microsoft .NET Framework 3.0 Service Pack 1, and Microsoft .NET Framework 3.5
Windows Server 2008 and Windows Server 2008 Service Pack 2 Microsoft .NET Framework 2.0 Service Pack 1, Microsoft .NET Framework 3.0 Service Pack 1, and Microsoft .NET Framework 3.5
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2 Microsoft .NET Framework 2.0 Service Pack 1, Microsoft .NET Framework 3.0 Service Pack 1, and Microsoft .NET Framework 3.5
Windows Server 2008 x64 Edition and Windows Server 2008 x64 Edition Service Pack 2 Microsoft .NET Framework 2.0 Service Pack 1, Microsoft .NET Framework 3.0 Service Pack 1, and Microsoft .NET Framework 3.5

The software in this list has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.

Why was this Bulletin revised on April 22, 2008?
This Bulletin was revised adding .NET Framework 1.0 (KB928367), .NET Framework 1.1 (KB928366), and .NET Framework Version 2.0 (KB928365) as affected components for Windows XP Service Pack 3. This is a detection update only. There were no changes to the binaries. Customers with Windows XP who have already installed the security update for .NET Framework 1.0, .NET Framework 1.1, and .NET Framework Version 2.0 will not need to reinstall the update after applying Windows XP Service Pack 3.

Why was this Bulletin revised on March 25, 2008?
This Bulletin was revised adding .NET Framework 1.0 (KB928367) and .NET Framework 1.1 (KB929729) as affected components for Windows Vista Service Pack 1 and Windows Server 2008. Customers with Windows Vista who have already installed the security update for .NET Framework 1.0 and .NET Framework 1.1 will not need to reinstall the update after applying Windows Vista Service Pack 1. By default, Windows Server 2008 does not include .NET Framework 1.0 or .NET Framework 1.1. Customers will only need to apply the update on Windows Server 2008 systems that have independently installed .NET Framework 1.0 or .NET Framework 1.1.

This security bulletin says that .NET Framework 3.0 is non-affected. How does .NET Framework 3.0 relate to the previous versions that are affected?
Microsoft .NET Framework 3.0 is a superset of .NET Framework 2.0. Microsoft .NET Framework 3.0 listed as Non-Affected Software in this security update refers to the four new technologies added as the superset to the .NET Framework 2.0. These technologies are: Windows Presentation Foundation (WPF), Windows Workflow Foundation (WF), Windows Communication Foundation (WCF), and Windows CardSpace. The vulnerabilities addressed in this security update do not affect any of the four specific .NET Framework 3.0 technologies. Developers wishing to learn more about the .NET Framework 3.0 and it’s relation to previous version may refer to the following .NET Framework 3.0 Versioning and Deployment MSDN article. Additional information for .NET Framework 3.0 may also be found in the following MSDN article.

I only have .NET Framework 3.0 installed. Why am I being offered the security update?
There is no security update targeting the WPF, WF, WCF, and CardSpace technologies that together make up Microsoft .NET Framework 3.0 as they are not affected by any of the vulnerabilities in this security update. However, every installation of Microsoft .NET Framework 3.0 also includes .NET Framework 2.0, which is an affected product in this security update and as such this update is offered to all systems where applicable.

What are the known issues that customers may experience when they install this security update?
Microsoft Knowledge Base Article 931212 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. In addition to the changes that are listed in the “Vulnerability Information” section of this bulletin, this update includes a defense-in-depth change to ASP.NET. This defense-in-depth change mitigates the issue reported publicly and assigned the Common Vulnerability and Exposure number CVE-2006-7192.

ASP.NET developed Web applications using the ASP.NET request validation feature can not replace an effective validation layer restricting untrusted input variables. Developers wishing to learn more about the security features that ASP.NET provides Web applications may refer to the following MSDN article.

How do I know if my ASP.NET Web application is vulnerable to this issue?
ASP.NET developed Web applications that restrict all untrusted input variables to a range of expected values or characters would not be affected. For more information on hardening ASP.NET Web applications see Microsoft Knowledge Base Article 815155.

Does this update contain any changes to functionality?
Yes. Besides the changes that are listed in the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the bulletin section, Vulnerability Information, this update includes changes not related to security. In addition to known issues related to this security update, Microsoft Knowledge Base Article 931212 documents functionality changes introduced in this .NET Framework security update.

Why does this update contain functionality changes that are non-security related?
All .NET Framework updates are cumulative, meaning security updates released may include functionality changes that have yet to be released in the next scheduled servicing method, such as a service pack.

Why was this bulletin updated with service pack information for the affected .NET Framework versions?
This bulletin was updated to provide additional clarification on the supported versions of the .NET Framework and which service packs apply to the affected products. Customers who have not installed a supported version of the .NET Framework will not be offered this update. Customers should upgrade the .NET Framework version on their system to a supported service pack before attempting to apply this update.

For additional information on the .NET Framework versions and their supported service packs, see Lifecycle Supported Service Packs.

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 version of the software discussed in this security bulletin. What should I do?
The affected software listed in this bulletin has been tested to determine which versions are affected. Other versions are past their support life cycle. To determine the support life cycle for your product and version, visit Microsoft Support Lifecycle.

It should be a priority for customers who have older versions of the software to migrate to supported versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the following Microsoft Support Lifecycle. For more information about the extended security update support period for these operating system versions, visit the Microsoft Product Support Services Web site.

Customers who require custom support for older software must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit the Microsoft Worldwide Information Web site, select the country, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Windows Operating System Product Support Lifecycle FAQ.

Vulnerability Information

Severity Ratings and Vulnerability Identifiers

Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected Software .NET PE Loader Vulnerability - CVE-2007-0041 ASP.NET Null Byte Termination Vulnerability - CVE-2007-0042 .NET JIT Compiler Vulnerability - CVE-2007-0043 Aggregate Severity Rating
Windows 2000
Microsoft .NET Framework 1.0 Service Pack 3 when installed on Windows 2000 Service Pack 4 Critical
Remote Code Execution
Important
Information Disclosure
None Critical
Microsoft .NET Framework 1.1 Service Pack 1 when installed on Windows 2000 Service Pack 4 Critical
Remote Code Execution
Important
Information Disclosure
None Critical
Microsoft .NET Framework 2.0 when installed on Windows 2000 Service Pack 4 Critical
Remote Code Execution
Important
Information Disclosure
Critical
Remote Code Execution
Critical
Windows XP
Microsoft .NET Framework 1.0 Service Pack 3 when installed on Windows XP Service Pack 2 and Windows XP Service Pack 3 Critical
Remote Code Execution
Important
Information Disclosure
None Critical
Microsoft .NET Framework 1.0 Service Pack 3 when installed on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 Critical
Remote Code Execution
Important
Information Disclosure
None Critical
Microsoft .NET Framework 1.0 Service Pack 3 on Windows XP Tablet PC Edition 2005 and Windows XP Media Center Edition 2005 Critical
Remote Code Execution
Important
Information Disclosure
None Critical
Microsoft .NET Framework 1.1 Service Pack 1 when installed on Windows XP Service Pack 2 and Windows XP Service Pack 3 Critical
Remote Code Execution
Important
Information Disclosure
None Critical
Microsoft .NET Framework 1.1 Service Pack 1 when installed on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 Critical
Remote Code Execution
Important
Information Disclosure
None Critical
Microsoft .NET Framework 2.0 when installed on Windows XP Service Pack 2 and Windows XP Service Pack 3 Critical
Remote Code Execution
Important
Information Disclosure
Critical
Remote Code Execution
Critical
Microsoft .NET Framework 2.0 when installed on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 Critical
Remote Code Execution
Important
Information Disclosure
Critical
Remote Code Execution
Critical
Windows Server 2003
Microsoft .NET Framework 1.0 Service Pack 3 when installed on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 Moderate
Remote Code Execution
Important
Information Disclosure
None Important
Microsoft .NET Framework 1.0 Service Pack 3 when installed on Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems Moderate
Remote Code Execution
Important
Information Disclosure
None Important
Microsoft .NET Framework 1.0 Service Pack 3 when installed on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 Moderate
Remote Code Execution
Important
Information Disclosure
None Important
Microsoft .NET Framework 1.1 Service Pack 1 on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 Moderate
Remote Code Execution
Important
Information Disclosure
None Important
Microsoft .NET Framework 1.1 Service Pack 1 when installed on Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems Moderate
Remote Code Execution
Important
Information Disclosure
None Important
Microsoft .NET Framework 1.1 Service Pack 1 when installed on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 Moderate
Remote Code Execution
Important
Information Disclosure
None Important
Microsoft .NET Framework 2.0 when installed on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 Moderate
Remote Code Execution
Important
Information Disclosure
Moderate
Remote Code Execution
Important
Microsoft .NET Framework 2.0 when installed on Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems Moderate
Remote Code Execution
Important
Information Disclosure
Moderate
Remote Code Execution
Important
Microsoft .NET Framework 2.0 when installed on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 Moderate
Remote Code Execution
Important
Information Disclosure
Moderate
Remote Code Execution
Important
Windows Vista Family
Microsoft .NET Framework 1.0 Service Pack 3 when installed on Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2 None Important
Information Disclosure
None Important
Microsoft .NET Framework 1.1 Service Pack 1 when installed on Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2 None Important
Information Disclosure
None Important
Microsoft .NET Framework 1.1 Service Pack 1 when installed on Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2 None Important
Information Disclosure
None Important
Microsoft .NET Framework 2.0 on Windows Vista None Important
Information Disclosure
None Important
Microsoft .NET Framework 2.0 on Windows Vista x64 Edition None Important
Information Disclosure
None Important
Windows Server 2008
Microsoft .NET Framework 1.0 Service Pack 3 when installed on Windows Server 2008 and Windows Server 2008 Service Pack 2 Moderate
Remote Code Execution
Important
Information Disclosure
None Important
Microsoft .NET Framework 1.1 Service Pack 1 when installed on Windows Server 2008 and Windows Server 2008 Service Pack 2 Moderate
Remote Code Execution
Important
Information Disclosure
None Important
Microsoft .NET Framework 1.1 Service Pack 1 when installed on Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2 Moderate
Remote Code Execution
Important
Information Disclosure
None Important
Microsoft .NET Framework 1.1 Service Pack 1 when installed on Windows Server 2008 x64 Edition and Windows Server 2008 x64 Edition Service Pack 2 Moderate
Remote Code Execution
Important
Information Disclosure
None Important

This assessment is based on the types of systems that are affected by the vulnerability, their typical deployment patterns, and the effect that exploiting the vulnerability would have on them.

.NET PE Loader Vulnerability - CVE-2007-0041:

A remote code execution vulnerability exists in .NET Framework that could allow an attacker who successfully exploited this vulnerability to make changes to the system with the permissions of the logged-on user. If a user is logged in 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.

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

Mitigating Factors for .NET PE Loader Vulnerability - CVE-2007-0041:

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 would have to host a Web site that contains a Web page that is used to exploit this vulnerability. An attacker would have no way to force users to visit a specially crafted Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link that takes them to the attacker's Web site. After they click the link, they would be prompted to perform several actions. An attack could only occur after they performed these actions.
  • 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 reduce the number of successful attacks that exploit this vulnerability by preventing Active Scripting and ActiveX controls from being used when reading HTML e-mail. However, if a user clicks on a link within an e-mail, they could still be vulnerable to this issue through the Web-based attack scenario.
  • By default, Internet Explorer on Windows Server 2003 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 have not been added to Internet Explorer Trusted sites zone. See the FAQ subsection of this vulnerability section for more information about Internet Explorer Enhanced Security Configuration.
  • .NET Framework 1.0 is not included in supported editions of Windows with the exception of the following:
    • Windows XP Tablet PC Edition 2005
    • Windows XP Media Center Edition 2005
  • .NET Framework 1.1 is not included in supported editions of Windows with the exception of the following:
    • Windows Server 2003 Service Pack 1
    • Windows Server 2003 Service Pack 2
  • .NET Framework 2.0 is not included in supported editions of Windows with the exception of the following:
    • Windows Vista and Windows Vista Service Pack 1
    • Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1

Workarounds for .NET PE Loader Vulnerability - CVE-2007-0041:

Microsoft has tested the following workarounds. Although these workarounds will not correct the underlying vulnerability, they help block known attack vectors. When a workaround reduces functionality, it is identified in the following section.

  • Set Internet and Local intranet security zone settings to “High” to prompt before running ActiveX Controls and Active Scripting in these zones.
    You can help protect against this vulnerability by changing your settings for the Internet security zone to prompt before running ActiveX controls. You can do this by setting your browser security to High.

    To raise the browsing security level in Microsoft Internet Explorer, follow these steps:

    1. On the Internet Explorer Tools menu, click Internet Options.
    2. In the Internet Options dialog box, click the Security tab, and then click the Internet icon.
    3. Under Security level for this zone, move the slider to High. This sets the security level for all Web sites you visit to High.

    Note If no slider is visible, click Default Level, and then move the slider to High.

    Note Setting the level to High may cause some Web sites to work incorrectly. If you have difficulty using a Web site after you change this setting, and you are sure the site is safe to use, you can add that site to your list of trusted sites. This will allow the site to work correctly even with the security setting set to High.

    Impact of Workaround: There are side effects to prompting before running ActiveX Controls and Active Scripting. Many Web sites that are on the Internet or on an intranet use ActiveX or Active Scripting to provide additional functionality. For example, an online e-commerce site or banking site may use ActiveX Controls to provide menus, ordering forms, or even account statements. Prompting before running ActiveX Controls or Active Scripting is a global setting that affects all Internet and intranet sites. You will be prompted frequently when you enable this workaround. For each prompt, if you feel you trust the site that you are visiting, click Yes to run ActiveX Controls or Active Scripting. If you do not want to be prompted for all these sites, use the steps outlined in "Add sites that you trust to the Internet Explorer Trusted sites zone”.

    Add sites that you trust to the Internet Explorer Trusted sites zone.

    After you set Internet Explorer to require a prompt before it runs ActiveX controls and Active Scripting in the Internet zone and in the Local intranet zone, you can add sites that you trust to the Internet Explorer Trusted sites zone. This will allow you to continue to use trusted Web sites exactly as you do today, while helping to protect you from this attack on untrusted sites. We recommend that you add only sites that you trust to the Trusted sites zone.

    To do this, follow these steps:

    1. In Internet Explorer, click Tools, click Internet Options, and then click the Security tab.
    2. In the Select a Web content zone to specify its current security settings box, click Trusted Sites, and then click Sites.
    3. If you want to add sites that do not require an encrypted channel, click to clear the Require server verification (https:) for all sites in this zone check box.
    4. In the Add this Web site to the zone box, type the URL of a site that you trust, and then click Add.
    5. Repeat these steps for each site that you want to add to the zone.
    6. Click OK two times to accept the changes and return to Internet Explorer.

    Note Add any sites that you trust not to take malicious action on your computer. Two in particular that you may want to add are "*.windowsupdate.microsoft.com" and “*.update.microsoft.com” (without the quotation marks). These are the sites that will host the update, and it requires an ActiveX Control to install the update.

  • Configure Internet Explorer to prompt before running Active Scripting or disable Active Scripting in the Internet and Local intranet security zone.
    You can help protect against this vulnerability by changing your settings to prompt before running Active Scripting or to disable Active Scripting in the Internet and Local intranet security zone. To do this, follow these steps:

    1. In Internet Explorer, click Internet Options on the Tools menu.
    2. Click the Security tab.
    3. Click Internet, and then click Custom Level.
    4. Under Settings, in the Scripting section, under Active Scripting, click Promptor Disable, and then click OK.
    5. Click Local intranet, and then click Custom Level.
    6. Under Settings, in the Scripting section, under Active Scripting, click Promptor Disable, and then click OK.
    7. Click OK two times to return to Internet Explorer.

    Note Disabling Active Scripting in the Internet and Local intranet security zones may cause some Web sites to work incorrectly. If you have difficulty using a Web site after you change this setting, and you are sure the site is safe to use, you can add that site to your list of trusted sites. This will allow the site to work correctly.

    Impact of Workaround: There are side effects to prompting before running Active Scripting. Many Web sites that are on the Internet or on an intranet use Active Scripting to provide additional functionality. For example, an online e-commerce site or banking site may use Active Scripting to provide menus, ordering forms, or even account statements. Prompting before running Active Scripting is a global setting that affects all Internet and intranet sites. You will be prompted frequently when you enable this workaround. For each prompt, if you feel you trust the site that you are visiting, click Yes to run Active Scripting. If you do not want to be prompted for all these sites, use the steps outlined in "Add sites that you trust to the Internet Explorer Trusted sites zone”.

    Add sites that you trust to the Internet Explorer Trusted sites zone.

    After you set Internet Explorer to require a prompt before it runs ActiveX controls and Active Scripting in the Internet zone and in the Local intranet zone, you can add sites that you trust to the Internet Explorer Trusted sites zone. This will allow you to continue to use trusted Web sites exactly as you do today, while helping to protect you from this attack on untrusted sites. We recommend that you add only sites that you trust to the Trusted sites zone.

    To do this, follow these steps:

    1. In Internet Explorer, click Tools, click Internet Options, and then click the Security tab.
    2. In the Select a Web content zone to specify its current security settings box, click Trusted Sites, and then click Sites.
    3. If you want to add sites that do not require an encrypted channel, click to clear the Require server verification (https:) for all sites in this zone check box.
    4. In the Add this Web site to the zone box, type the URL of a site that you trust, and then click Add.
    5. Repeat these steps for each site that you want to add to the zone.
    6. Click OK two times to accept the changes and return to Internet Explorer.

    Note Add any sites that you trust not to take malicious action on your computer. Two in particular that you may want to add are "*.windowsupdate.microsoft.com" and “*.update.microsoft.com” (without the quotation marks). These are the sites that will host the update, and it requires an ActiveX Control to install the update.

  • Read e-mail messages in plain text format to help protect yourself from the HTML e-mail attack vector
    You can help protect yourself against this vulnerability by changing your e-mail settings to read e-mail messages in plain text using Outlook 2002 and later, Outlook Express 6 and later, or Windows Mail. For information in Outlook, search “plain text” in Help and review “Read messages in plain text.” In Outlook Express, search “plain text” in Help and review “Reducing your risk of getting e-mail viruses.” In Windows Mail, search “plain text” in Help and review “Security and privacy in Windows Mail.”

    Impact of Workaround: E-mail messages that are viewed in plain text format will not contain pictures, specialized fonts, animations, or other rich content. Additionally:

    • The changes are applied to the preview pane and to open messages.
    • Pictures become attachments so that they are not lost.
    • Because the message is still in Rich Text or HTML format in the store, the object model (custom code solutions) may behave unexpectedly.
  • Disable .Net controls in Internet Explorer 7
    You can help protect against this vulnerability by changing your settings to disable .NET controls in the Internet and Local intranet security zone. To do this, follow these steps:

    1. In Internet Explorer 7, click Internet Options on the Tools menu.
    2. Click the Security tab.
    3. Click Internet, and then click Custom Level.
    4. Change the following options to Disabled:
    5. .Net Framework
    6. Loose XAML
    7. XAML browser applications
    8. XPS documents
    9. .Net Framework-reliant components
    10. Run components not signed with Authenticode
    11. Run components signed with Authenticode
    12. Click OK to save the changes
    13. Make the same changes in other risk zones.
    14. Click OK two times to return to Internet Explorer.

    Impact of workaround: .NET controls will not load in the zones you have configured.

FAQ for .NET PE Loader Vulnerability - CVE-2007-0041:

What is the scope of the vulnerability?
If successfully exploited, this remote code execution vulnerability could allow the attacker to run arbitrary code as the logged-on user.

What causes the vulnerability?
An unchecked buffer in the .NET Framework PE Loader service.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could make changes to the system with the permissions of the logged-on user. If a user is logged in 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 host a specially crafted Web site that is designed to exploit this vulnerability through Internet Explorer and then persuade a user to view the Web site. This can also include Web sites that accept user-provided content or advertisements, Web sites that host user-provided content or advertisements, and compromised Web sites. 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 persuade 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. After they click the link, they would be prompted to perform several actions. An attack could only occur after they performed these actions. 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 is logged on and visits a Web site or runs a .NET application locally 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.

I am running Internet Explorer for Windows Server 2003. Does this mitigate this vulnerability?
Yes. By default, Internet Explorer for Windows Server 2003 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 malicious 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 does the update do?
The update removes the vulnerability by modifying the way that .NET Framework PE Loader validates the length of a message before it passes the message to the allocated buffer.

When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure.

ASP.NET Null Byte Termination Vulnerability - CVE-2007-0042:

An information disclosure vulnerability exists in .NET Framework that could allow an attacker who successfully exploited this vulnerability to bypass the security features of an ASP.NET Web site to download the contents of any Web page.

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

Mitigating Factors for ASP.NET Null Byte Termination Vulnerability - CVE-2007-0042:

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 factor may be helpful in your situation:

ASP.NET developed Web applications that restrict all untrusted input variables, including null bytes, to a range of expected values or characters would not be affected. Developers wishing to learn more about the security features that ASP.NET provides Web applications may refer to the following MSDN article.

Workarounds for ASP.NET Null Byte Termination Vulnerability - CVE-2007-0042:

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 workaround and states in the discussion whether a workaround reduces functionality:

ASP.NET Web Developers may compare values obtained from Internet accessible values such as query string, cookies, or form variables against a list of allowed values and reject any other values that fall outside of this range.

FAQ for ASP.NET Null Byte Termination Vulnerability - CVE-2007-0042:

What is the scope of the vulnerability?
This information disclosure vulnerability could allow an attacker to bypass ASP.NET security features by sending invalid URLs and gaining unauthorized access to configuration files. Note that this vulnerability would not allow an attacker to execute code or to elevate their user rights directly, but it could be used to find information that could be used to try to further compromise the affected system.

What causes the vulnerability?
ASP.NET does not properly validate the URL passed as input.

What is ASP.NET?
ASP.NET is a collection of technologies within the.NET Framework that enable developers to build Web applications and XML Web Services.

Unlike traditional Web pages, which use a combination of static HTML and scripting, ASP.NET uses compiled, event-driven pages. Because ASP.NET is a Web-based application environment, requiring an underlying Web server to provide basic HTTP functionality. ASP.NET runs on top of Internet Information Services (IIS) 5.0 on Windows 2000, IIS 5.1 on Windows XP, and IIS 6.0 on Windows Server 2003.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could gain unauthorized access to parts of a Web site. The actions the attacker could take would depend on the specific content being protected.

Who could exploit the vulnerability?
In a Web-based attack scenario, an anonymous user who could connect to a Web site with a specially crafted URL could try to exploit this vulnerability.

What systems are primarily at risk from the vulnerability?
Internet-facing systems that host Web sites are primarily at risk from this vulnerability.

What does the update do?
The update removes the vulnerability by modifying the way that ASP.NET validates URLs.

When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure.

.NET JIT Compiler Vulnerability - CVE-2007-0043:

A remote code execution vulnerability exists in .NET Framework Just In Time Compiler that could allow an attacker who successfully exploited this vulnerability to make changes to the system with the permissions of the logged-on user. If a user is logged on with administrative user rights, an attacker could take complete control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

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

Mitigating Factors for .NET JIT Compiler Vulnerability - CVE-2007-0043:

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 would have to host a Web site that contains a Web page that is used to exploit this vulnerability. An attacker would have no way to force users to visit a specially crafted Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link that takes them to the attacker's Web site. After they click the link, they would be prompted to perform several actions. An attack could only occur after they performed these actions.
  • 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 reduce the number of successful attacks that exploit this vulnerability by preventing Active Scripting and ActiveX controls from being used when reading HTML e-mail. However, if a user clicks on a link within an e-mail, they could still be vulnerable to this issue through the Web-based attack scenario.
  • By default, Internet Explorer on Windows Server 2003 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 have not been added to Internet Explorer Trusted sites zone. See the FAQ subsection of this vulnerability section for more information about Internet Explorer Enhanced Security Configuration.
  • .NET Framework 1.0 is not included in supported editions of Windows with the exception of the following:
    • Windows XP Tablet PC Edition 2005
    • Windows XP Media Center Edition 2005
  • .NET Framework 1.1 is not included in supported editions of Windows with the exception of the following:
    • Windows Server 2003 Service Pack 1
    • Windows Server 2003 Service Pack 2
  • .NET Framework 2.0 is not included in supported editions of Windows with the exception of the following:
    • Windows Vista and Windows Vista Service Pack 1
    • Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1

Workarounds for .NET JIT Compiler Vulnerability - CVE-2007-0043:

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:

  • Set Internet and Local intranet security zone settings to “High” to prompt before running ActiveX Controls and Active Scripting in these zones.
    You can help protect against this vulnerability by changing your settings for the Internet security zone to prompt before running ActiveX controls. You can do this by setting your browser security to High.

    To raise the browsing security level in Microsoft Internet Explorer, follow these steps:

    1. On the Internet Explorer Tools menu, click Internet Options.
    2. In the Internet Options dialog box, click the Security tab, and then click the Internet icon.
    3. Under Security level for this zone, move the slider to High. This sets the security level for all Web sites you visit to High.

      Note If no slider is visible, click Default Level, and then move the slider to High.

      Note Setting the level to High may cause some Web sites to work incorrectly. If you have difficulty using a Web site after you change this setting, and you are sure the site is safe to use, you can add that site to your list of trusted sites. This will allow the site to work correctly even with the security setting set to High.

    Impact of Workaround: There are side effects to prompting before running ActiveX Controls and Active Scripting. Many Web sites that are on the Internet or on an intranet use ActiveX or Active Scripting to provide additional functionality. For example, an online e-commerce site or banking site may use ActiveX Controls to provide menus, ordering forms, or even account statements. Prompting before running ActiveX Controls or Active Scripting is a global setting that affects all Internet and intranet sites. You will be prompted frequently when you enable this workaround. For each prompt, if you feel you trust the site that you are visiting, click Yes to run ActiveX Controls or Active Scripting. If you do not want to be prompted for all these sites, use the steps outlined in "Add sites that you trust to the Internet Explorer Trusted sites zone”.

    Add sites that you trust to the Internet Explorer Trusted sites zone.

    After you set Internet Explorer to require a prompt before it runs ActiveX controls and Active Scripting in the Internet zone and in the Local intranet zone, you can add sites that you trust to the Internet Explorer Trusted sites zone. This will allow you to continue to use trusted Web sites exactly as you do today, while helping to protect you from this attack on untrusted sites. We recommend that you add only sites that you trust to the Trusted sites zone.

    To do this, follow these steps:

    1. In Internet Explorer, click Tools, click Internet Options, and then click the Security tab.
    2. In the Select a Web content zone to specify its current security settings box, click Trusted Sites, and then click Sites.
    3. If you want to add sites that do not require an encrypted channel, click to clear the Require server verification (https:) for all sites in this zone check box.
    4. In the Add this Web site to the zone box, type the URL of a site that you trust, and then click Add.
    5. Repeat these steps for each site that you want to add to the zone.
    6. Click OK two times to accept the changes and return to Internet Explorer.

      Note Add any sites that you trust not to take malicious action on your computer. Two in particular that you may want to add are "*.windowsupdate.microsoft.com" and “*.update.microsoft.com” (without the quotation marks). These are the sites that will host the update, and it requires an ActiveX Control to install the update.

  • Configure Internet Explorer to prompt before running Active Scripting or disable Active Scripting in the Internet and Local intranet security zone.
    You can help protect against this vulnerability by changing your settings to prompt before running Active Scripting or to disable Active Scripting in the Internet and Local intranet security zone. To do this, follow these steps:

    1. In Internet Explorer, click Internet Options on the Tools menu.
    2. Click the Security tab.
    3. Click Internet, and then click Custom Level.
    4. Under Settings, in the Scripting section, under Active Scripting, click Promptor Disable, and then click OK.
    5. Click Local intranet, and then click Custom Level.
    6. Under Settings, in the Scripting section, under Active Scripting, click Promptor Disable, and then click OK.
    7. Click OK two times to return to Internet Explorer.

    Note Disabling Active Scripting in the Internet and Local intranet security zones may cause some Web sites to work incorrectly. If you have difficulty using a Web site after you change this setting, and you are sure the site is safe to use, you can add that site to your list of trusted sites. This will allow the site to work correctly.

    Impact of Workaround: There are side effects to prompting before running Active Scripting. Many Web sites that are on the Internet or on an intranet use Active Scripting to provide additional functionality. For example, an online e-commerce site or banking site may use Active Scripting to provide menus, ordering forms, or even account statements. Prompting before running Active Scripting is a global setting that affects all Internet and intranet sites. You will be prompted frequently when you enable this workaround. For each prompt, if you feel you trust the site that you are visiting, click Yes to run Active Scripting. If you do not want to be prompted for all these sites, use the steps outlined in "Add sites that you trust to the Internet Explorer Trusted sites zone”.

    Add sites that you trust to the Internet Explorer Trusted sites zone.

    After you set Internet Explorer to require a prompt before it runs ActiveX controls and Active Scripting in the Internet zone and in the Local intranet zone, you can add sites that you trust to the Internet Explorer Trusted sites zone. This will allow you to continue to use trusted Web sites exactly as you do today, while helping to protect you from this attack on untrusted sites. We recommend that you add only sites that you trust to the Trusted sites zone.

    To do this, follow these steps:

    1. In Internet Explorer, click Tools, click Internet Options, and then click the Security tab.
    2. In the Select a Web content zone to specify its current security settings box, click Trusted Sites, and then click Sites.
    3. If you want to add sites that do not require an encrypted channel, click to clear the Require server verification (https:) for all sites in this zone check box.
    4. In the Add this Web site to the zone box, type the URL of a site that you trust, and then click Add.
    5. Repeat these steps for each site that you want to add to the zone.
    6. Click OK two times to accept the changes and return to Internet Explorer.

    Note Add any sites that you trust not to take malicious action on your computer. Two in particular that you may want to add are "*.windowsupdate.microsoft.com" and “*.update.microsoft.com” (without the quotation marks). These are the sites that will host the update, and it requires an ActiveX Control to install the update.

  • Read e-mail messages in plain text format to help protect yourself from the HTML e-mail attack vector
    You can help protect yourself against this vulnerability by changing your e-mail settings to read e-mail messages in plain text using Outlook 2002 and later, Outlook Express 6 and later, or Windows Mail. For information in Outlook, search “plain text” in Help and review “Read messages in plain text.” In Outlook Express, search “plain text” in Help and review “Reducing your risk of getting e-mail viruses.” In Windows Mail, search “plain text” in Help and review “Security and privacy in Windows Mail.”

    Impact of Workaround: E-mail messages that are viewed in plain text format will not contain pictures, specialized fonts, animations, or other rich content. Additionally:

    • The changes are applied to the preview pane and to open messages.
    • Pictures become attachments so that they are not lost.
    • Because the message is still in Rich Text or HTML format in the store, the object model (custom code solutions) may behave unexpectedly.

FAQ .NET JIT Compiler Vulnerability - CVE-2007-0043:

What is the scope of the vulnerability?
If successfully exploited, this remote code execution vulnerability could allow the attacker to run arbitrary code as the logged-on user.

What causes the vulnerability?
An unchecked buffer in the .NET Framework 2.0 JIT Compiler service within the .NET Framework.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could make changes to the system with the permissions of the logged-on user. If a user is logged on with administrative user rights, an attacker could take complete control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

How could an attacker exploit the vulnerability?
An attacker could host a specially crafted Web site that is designed to exploit this vulnerability through Internet Explorer and then persuade a user to view the Web site. This can also include Web sites that accept user-provided content or advertisements, Web sites that host user-provided content or advertisements, and compromised Web sites. 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 persuade 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 is logged on and visits 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.

I am running Internet Explorer for Windows Server 2003. Does this mitigate this vulnerability?
Yes. By default, Internet Explorer for Windows Server 2003 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 malicious 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 does the update do?
The update removes the vulnerability by modifying the way that the .NET Framework 2.0 JIT Compiler validates the length of a message before it passes the message to the allocated buffer.

When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure.

Update Information

Detection and Deployment Tools and Guidance

Manage the software and security updates you need to deploy to the servers, desktop, and mobile computers in your organization. For more information see the TechNet Update Management Center. The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.

Security updates are available from Microsoft Update, Windows Update, and Office Update. Security updates are also available at the Microsoft Download Center. You can find them most easily by doing a keyword search for "security_patch." Finally, security updates can be downloaded from the Windows Update Catalog. For more information about the Windows Update Catalog, see Microsoft Knowledge Base Article 323166.

Detection and Deployment Guidance

Microsoft has provided detection and deployment guidance for this month’s security updates. This guidance will also help IT professionals understand how they can use various tools to help deploy the security update, such as Windows Update, Microsoft Update, Office Update, the Microsoft Baseline Security Analyzer (MBSA), the Office Detection Tool, Microsoft Systems Management Server (SMS), the Extended Security Update Inventory Tool, and the Enterprise Update Scan Tool (EST). For more information, see Microsoft Knowledge Base Article 910723.

Microsoft Baseline Security Analyzer and Enterprise Update Scan Tool (EST)

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.

MBSA 1.2.1 does not support detection for this security update. The Enterprise Update Scan Tool does, and is what customers can use instead of MBSA 1.2.1. For download links and more information about the version of EST that is being released this month, see Microsoft Knowledge Base Article 894193. SMS customers should also see the heading, Systems Management Server, for more information about SMS and EST.

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

Software MBSA 1.2.1 EST MBSA 2.0.1
Microsoft .NET Framework 1.0 Service Pack 3 No Yes Yes See Note for Windows Vista below
Microsoft .NET Framework 1.1 Service Pack 1 No Yes Yes See Note for Windows Vista below
Microsoft .NET Framework 2.0 No Yes Yes See Note for Windows Vista below

Note for Windows Vista Microsoft does not support installing MBSA 2.0.1 on computers that run Windows Vista, but you may install MBSA 2.0.1 on a supported operating system and then scan the Windows Vista-based computer remotely. For additional information about MBSA support for Windows Vista, visit the Microsoft Baseline Security Analyzer. See also Microsoft Knowledge Base Article 931943: Microsoft Baseline Security Analyzer (MBSA) support for Windows Vista.

For more information about MBSA, visit the Microsoft Baseline Security Analyzer. For more information about the software that Microsoft Update and MBSA 2.0 currently do not detect, see Microsoft Knowledge Base Article 895660.

Windows Server Update Services

By using Windows Server Update Services (WSUS), administrators can deploy the latest critical updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000 to Windows 2000 and later operating systems. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services.

Systems Management Server

The following table provides the SMS detection and deployment summary for this security update.

Software SMS 2.0 SMS 2003
Microsoft .NET Framework 1.0 Service Pack 3 Yes (with EST) Yes
Microsoft .NET Framework 1.1 Service Pack 1 Yes (with EST) Yes
Microsoft .NET Framework 2.0 Yes (with EST) Yes

SMS 2.0 and SMS 2003 Software Update Services (SUS) Feature Pack can use MBSA 1.2.1 for detection and therefore have the same limitation listed earlier relating to programs that MBSA 1.2.1 does not detect.

For SMS 2.0, the SMS SUS Feature Pack, which includes the Security Update Inventory Tool (SUIT), can be used by SMS to detect security updates. SMS SUIT uses the MBSA 1.2.1 engine for detection. For more information about SUIT, visit the following Microsoft Knowledge Base Article 894154. For more information about the limitations of SUIT, see Microsoft Knowledge Base Article 306460. The SMS SUS Feature Pack also includes the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.

For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, visit the following Microsoft Web site. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.

Note for Windows Vista Microsoft Systems Management Server 2003 with Service Pack 3 includes support for Windows Vista manageability.

For more information about SMS, visit the Systems Management Server.

For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles.

Security Update Deployment

Affected Software

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

Microsoft .NET Framework 1.0 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 The update for this issue may be included in a future update rollup
Deployment
Installing without user intervention Microsoft .NET Framework 1.0 (KB928367):
NDP1.0sp3-KB928367-x86-enu /q
Microsoft .NET Framework 1.0 (KB930494):
NDP1.0sp3-KB930494-x86-ocm-enu /quiet
Installing without restarting Microsoft .NET Framework 1.0 (KB928367):
NDP1.0sp3-KB928367-x86-enu /q
Microsoft .NET Framework 1.0 (KB930494):
NDP1.0sp3-KB930494-x86-ocm-enu /norestart
Further information See the subsection, Microsoft Detection and Deployment Tools and Guidance
Restart Requirement
Restart required You must restart your system after you apply this security update
Hotpatching Not applicable
Removal Information Microsoft .NET Framework 1.0 (KB928367):
Use Add or Remove Programs tool in Control Panel
Microsoft .NET Framework 1.0 (KB930494):
Use Add or Remove Programs tool in Control Panel
File Information See the subsection, File Information, in this section for the full file manifest
Registry Key Verification Microsoft .NET Framework 1.0 (KB928367):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates.NETFramework\1.0\M928367
Microsoft .NET Framework 1.0 (KB930494):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB930494

File Information

The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Microsoft .NET Framework 1.0 (KB928367):

File Name Version Date Time Size
Aspnet_isapi.dll 1.0.3705.6060 03-Jan-2007 00:34 200,704
Aspnet_wp.exe 1.0.3705.6060 03-Jan-2007 00:34 32,768
Ieexec.exe 1.0.3705.6060 03-Jan-2007 00:29 8,192
Mscorie.dll 1.0.3705.6060 03-Jan-2007 00:29 73,728
Mscorld.dll 1.0.3705.6060 03-Jan-2007 00:29 86,016
Mscorlib.dll 1.0.3705.6060 03-Jan-2007 00:21 1,998,848
Mscorlib.ldo N/A 03-Jan-2007 00:22 10,436
Mscorsvr.dll 1.0.3705.6060 03-Jan-2007 00:28 2,273,280
Mscorwks.dll 1.0.3705.6060 03-Jan-2007 00:28 2,281,472
System.web.dll 1.0.3705.6060 03-Jan-2007 00:40 1,200,128

Microsoft .NET Framework 1.0 (KB930494):

File Name Version Date Time Size
Aspnet_isapi.dll 1.0.3705.6060 03-Jan-2007 00:34 200,704
Aspnet_wp.exe 1.0.3705.6060 03-Jan-2007 00:34 32,768
Gacutil.exe 1.0.3705.0 16-Jan-2007 00:09 61,440
Ieexec.exe 1.0.3705.6060 03-Jan-2007 00:29 8,192
Mscorie.dll 1.0.3705.6060 03-Jan-2007 00:29 73,728
Mscorld.dll 1.0.3705.6060 03-Jan-2007 00:29 86,016
Mscorlib.dll 1.0.3705.6060 03-Jan-2007 00:21 1,998,848
Mscorlib.ldo N/A 03-Jan-2007 00:22 10,436
Mscorsvr.dll 1.0.3705.6060 03-Jan-2007 00:28 2,273,280
Mscorwks.dll 1.0.3705.6060 03-Jan-2007 00:28 2,281,472
Netfxupdate.exe 1.0.3705.3 16-Jan-2007 00:11 73,728
Setregni.exe 1.1.4322.2035 16-Jan-2007 00:11 57,344
System.web.dll 1.0.3705.6060 03-Jan-2007 00:40 1,200,128
Togac.exe 1.1.4322.2251 16-Jan-2007 00:11 57,344
Ddpatchui.msm N/A 15-Jan-2007 23:21 15,360
Preinstall.exe 1.1.0.2 16-Jan-2007 00:11 57,344

Note For a complete list of supported versions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.

Deployment Information

Installing the Update

When you install this security update, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

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

This security update supports the following setup switches.

Microsoft .NET Framework 1.0 (KB928367):

Supported Security Update Installation Switches
Switch Description
/?
Displays the command-line options.
Setup Modes
/q Quiet installation.
Install Options
/I Install (default action).
/U Uninstall.
/Xp[:path] Extract the package to the specified directory.
Restart Options
/q Does not restart when installation has completed.
Logging Options
/l <LogFile> Generate Log file.
/l[d|p|f] <LogFile> d - Log package details
p - Log affected products
f - Log included files

Microsoft .NET Framework 1.0 (KB930494):

Supported Security Update Installation Switches
Switch Description
/?
Displays the command-line options.
Setup Modes
/q Quiet mode - same as unattended mode, but no status or error messages are displayed.
Install Options
/forceappsclose Forces other programs to close when the computer shuts down.
/nobackup Forces other programs to close when the computer shuts down.
/overwriteoem Overwrite OEM files without prompting.
/integrate: path Integrates the software updates into the Windows installation source files located at the path specified. Note that :path refers to the folder that contains the i386 folder.
/ER Enable extended error reporting.
/d: path Specifies a backup directory for Windows Service Pack installation. :path indicates the destination folder for the backup files. The default backup location is %Systemdrive%\$ntservicepackuninstall$.
/hotpatch:disable Disables hotpatching functionality, and installs the cold patch only.
Restart Options
/norestart Do not restart the computer when the installation is finished.
/warnrestart Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (Default is 30 sec). Intended for use with either /quiet or /passive switches.
/forcerestart Restart the computer after installation and force other applications to close at shutdown without saving open files first.
/promptrestart Presents a dialog box to prompt user to restart if required. Intended for use with /quiet.
Logging Options
/log:path Allows user to specify where to create the log file.
/verbose Enable verbose logging. Creates %Windir%\CabBuild.log upon install that details files to be copied. Using this switch may cause the installation to occur much slower.

Verifying Update Installation

  • 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 of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

      Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.

    5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.

      Note Attributes other than 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 the update installation. 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 .NET Framework 1.1 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 The update for this issue may be included in a future update rollup
Deployment
Installing without user intervention Microsoft .NET Framework 1.1 (KB928366):
NDP1.1sp1-KB928366-x86 /q
Microsoft .NET Framework 1.1 (KB933854):
WindowsServer2003-KB933854-x86-enu /quiet
Microsoft .NET Framework 1.1 (KB929729):
NDP1.1sp1-KB929729-x86 /q
Installing without restarting Microsoft .NET Framework 1.1 (KB928366):
NDP1.1sp1-KB928366-x86 /q
Microsoft .NET Framework 1.1 (KB933854):
WindowsServer2003-KB933854-x86-enu /norestart
Microsoft .NET Framework 1.1 (KB929729):
NDP1.1sp1-KB929729-x86 /q
Update log file Microsoft .NET Framework 1.1 (KB933854):
KB933854.log
Further information See the subsection, Microsoft Detection and Deployment Tools and Guidance
Restart Requirement
Restart required You must restart your system after you apply this security update
Hotpatching Not applicable
Removal Information Microsoft .NET Framework 1.1 (KB928366):
Use Add or Remove Programs tool in Control Panel
Microsoft .NET Framework 1.1 (KB933854):
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the Use the Spuninst.exe utility, located in the %Windir%$NTUninstallKB933854$\Spuninst folder
Microsoft .NET Framework 1.1 (KB929729):
Use Add or Remove Programs tool in Control Panel
File Information See the subsection, File Information, in this section for the full file manifest
Registry Key Verification Microsoft .NET Framework 1.1 (KB928366):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates.NETFramework\1.1\M928366
Microsoft .NET Framework 1.1 (KB933854):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB933854
Microsoft .NET Framework 1.1 (KB929729):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates.NETFramework\1.1\M929729

File Information

The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Microsoft .NET Framework 1.1 (KB928366):

File Name Version Date Time Size
Aspnet_isapi.dll 1.1.4322.2407 14-Apr-2007 04:30 258,048
Aspnet_wp.exe 1.1.4322.2407 14-Apr-2007 04:30 32,768
Corperfmonext.dll 1.1.4322.2407 14-Apr-2007 03:57 81,920
Mscoree.dll 2.0.50727.253 22-Dec-2006 20:28 271,360
Mscorees.dll 2.0.50727.253 22-Dec-2006 21:02 6,144
Mscorie.dll 1.1.4322.2407 14-Apr-2007 03:57 86,016
Mscorjit.dll 1.1.4322.2407 14-Apr-2007 03:56 315,392
Mscorld.dll 1.1.4322.2407 14-Apr-2007 03:58 102,400
Mscorlib.dll 1.1.4322.2407 14-Apr-2007 03:50 2,142,208
Mscorlib.ldo N/A 14-Apr-2007 03:52 10,952
Mscorsn.dll 1.1.4322.2407 14-Apr-2007 03:58 77,824
Mscorsvr.dll 1.1.4322.2407 14-Apr-2007 03:57 2,523,136
Mscorwks.dll 1.1.4322.2407 14-Apr-2007 03:57 2,514,944
System.dll 1.1.4322.2407 14-Apr-2007 04:35 1,232,896
System.ldo N/A 14-Apr-2007 04:34 11,540
System.web.dll 1.1.4322.2407 14-Apr-2007 04:35 1,265,664

Microsoft .NET Framework 1.1 (KB933854):

File Name Version Date Time Size
Aspnet_isapi.dll 1.1.4322.2407 20-Apr-2007 08:10 258,048
Aspnet_wp.exe 1.1.4322.2407 20-Apr-2007 08:10 32,768
Corperfmonext.dll 1.1.4322.2407 20-Apr-2007 08:10 81,920
Mscoree.dll 2.0.50727.253 20-Apr-2007 08:10 271,360
Mscorees.dll 2.0.50727.253 08-Mar-2007 07:15 6,144
Mscorie.dll 1.1.4322.2407 20-Apr-2007 08:10 86,016
Mscorld.dll 1.1.4322.2407 20-Apr-2007 08:10 102,400
Mscorlib.dll 1.1.4322.2407 18-Apr-2007 07:25 2,142,208
Mscorlib.ldo N/A 20-Apr-2007 19:09 10,952
Mscorsn.dll 1.1.4322.2407 20-Apr-2007 08:10 77,824
Mscorsvr.dll 1.1.4322.2407 20-Apr-2007 08:10 2,523,136
Mscorwks.dll 1.1.4322.2407 20-Apr-2007 08:10 2,514,944
Netfxupdate.exe 1.0.3705.3 08-Mar-2007 13:44 73,728
Setregni.exe 1.1.4322.2034 08-Mar-2007 13:44 106,496
Sy52106.dll 1.1.4322.2407 18-Apr-2007 07:25 1,232,896
System.ldo N/A 20-Apr-2007 19:10 11,540
System.web.dll 1.1.4322.2407 18-Apr-2007 07:25 1,265,664
Togac.exe 1.1.4322.573 20-Apr-2007 08:10 118,784

Microsoft .NET Framework 1.1 (KB929729):

File Name Version Date Time Size
Aspnet_isapi.dll 1.1.4322.2407 14-Apr-2007 04:30 258,048
Aspnet_wp.exe 1.1.4322.2407 14-Apr-2007 04:30 32,768
Corperfmonext.dll 1.1.4322.2407 14-Apr-2007 03:57 81,920
Mscorie.dll 1.1.4322.2407 14-Apr-2007 03:57 86,016
Mscorjit.dll 1.1.4322.2407 14-Apr-2007 03:56 315,392
Mscorld.dll 1.1.4322.2407 14-Apr-2007 03:58 102,400
Mscorlib.dll 1.1.4322.2407 14-Apr-2007 03:50 2,142,208
Mscorlib.ldo N/A 14-Apr-2007 03:52 10,952
Mscorsn.dll 1.1.4322.2407 14-Apr-2007 03:58 77,824
Mscorsvr.dll 1.1.4322.2407 14-Apr-2007 03:57 2,523,136
Mscorwks.dll 1.1.4322.2407 14-Apr-2007 03:57 2,514,944
System.dll 1.1.4322.2407 14-Apr-2007 04:35 1,232,896
System.ldo N/A 14-Apr-2007 04:34 11,540
System.web.dll 1.1.4322.2407 14-Apr-2007 04:35 1,265,664

Deployment Information

Installing the Update

When you install this security update, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

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

This security update supports the following setup switches.

Microsoft .NET Framework 1.1 (KB928366):

Supported Security Update Installation Switches
Switch Description
/?
Displays the command-line options.
Setup Modes
/q Quiet installation.
Install Options
/I Install (default action).
/U Uninstall.
/Xp[:path] Extract the package to the specified directory.
Restart Options
/q Does not restart when installation has completed.
Logging Options
/l <LogFile> Generate Log file.
/l[d|p|f] <LogFile> d - Log package details
p - Log affected products
f - Log included files

Microsoft .NET Framework 1.1 (KB933854):

Supported Security Update Installation Switches
Switch Description
/help Displays the command-line options
Setup Modes
/passive Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart Does not restart when installation has completed
/forcerestart Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x] Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart Display a dialog box prompting the local user to allow a restart
Special Options
/overwriteoem Overwrites OEM files without prompting
/nobackup Does not back up files needed for uninstall
/forceappsclose Forces other programs to close when the computer shuts down
/log:path Allows the redirection of installation log files
/integrate:path Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.
/extract[:path] Extracts files without starting the Setup program
/ER Enables extended error reporting
/verbose Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.

Microsoft .NET Framework 1.1 (KB929729):

Supported Security Update Installation Switches
Switch Description
/?
Displays the command-line options.
Setup Modes
/q Quiet installation.
Install Options
/I Install (default action).
/U Uninstall.
/Xp[:path] Extract the package to the specified directory.
Restart Options
/q Does not restart when installation has completed.
Logging Options
/l <LogFile> Generate Log file.
/l[d|p|f] <LogFile> d - Log package details
p - Log affected products
f - Log included files

Verifying Update Installation

  • 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 of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

      Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.

    5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.

      Note Attributes other than 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 the update installation. 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 .NET Framework 2.0

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 Microsoft .NET Framework 2.0 (KB928365):
NDP20-KB928365-x86 /qn
Microsoft .NET Framework 2.0 (KB929916):
Windows6.0-KB929916-x86 /quiet
Installing without restarting Microsoft .NET Framework 2.0 (KB928365):
NDP20-KB928365-x86 /norestart
Microsoft .NET Framework 2.0 (KB929916):
Windows6.0-KB929916-x86 /norestart
Further information See the subsection, Microsoft Detection and Deployment Tools and Guidance
Restart Requirement
Restart required You must restart your system after you apply this security update
Hotpatching Not applicable
Removal Information Microsoft .NET Framework 2.0 (KB928365):
Use Add or Remove Programs tool in Control Panel
Microsoft .NET Framework 2.0 (KB929916):
Use Add or Remove Programs tool in Control Panel
File Information See the subsection, File Information, in this section for the full file manifest
Registry Key Verification Microsoft .NET Framework 2.0 (KB928365):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 2.0\KB928365
Microsoft .NET Framework 2.0 (KB929916):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB929916

File Information

The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Microsoft .NET Framework 2.0 (KB928365):

File Name Version Date Time Size
Applaunch.exe 2.0.50727.832 13-Apr-2007 03:21 58,712
Aspnet.mof N/A 13-Apr-2007 03:20 53,674
Aspnetmmcext.dll 2.0.50727.832 13-Apr-2007 03:20 507,904
Aspnet_filter.dll 2.0.50727.832 13-Apr-2007 03:20 10,752
Aspnet_isapi.dll 2.0.50727.832 13-Apr-2007 03:20 8,192
Aspnet_perf.dll 2.0.50727.832 13-Apr-2007 03:20 23,552
Aspnet_perf.ini N/A 13-Apr-2007 03:20 777,248
Aspnet_perf2.ini N/A 13-Apr-2007 03:20 775,652
Aspnet_rc.dll 2.0.50727.832 13-Apr-2007 03:20 75,264
Aspnet_regiis.exe 2.0.50727.832 13-Apr-2007 03:20 32,608
Aspnet_state.exe 2.0.50727.832 13-Apr-2007 03:20 33,632
Aspnet_state_perf.ini N/A 13-Apr-2007 03:20 42,868
Aspnet_wp.exe 2.0.50727.832 13-Apr-2007 03:20 32,600
Corperfmonext.dll 2.0.50727.832 13-Apr-2007 03:21 88,576
Dfsvc.exe 2.0.50727.832 13-Apr-2007 03:20 5,120
Ieexec.exe 2.0.50727.832 13-Apr-2007 03:21 9,728
Ilasm.exe 2.0.50727.832 13-Apr-2007 03:21 228,688
Installutil.exe 2.0.50727.832 13-Apr-2007 03:21 28,672
Microsoft.build.engine.dll 2.0.50727.832 13-Apr-2007 03:21 413,696
Microsoft.build.tasks.dll 2.0.50727.832 13-Apr-2007 03:21 647,168
Microsoft.common.targets N/A 13-Apr-2007 03:21 177,541
Microsoft.jscript.dll 8.0.50727.832 13-Apr-2007 03:21 749,568
Mmcaspext.dll 2.0.50727.832 13-Apr-2007 03:20 87,040
Mscordacwks.dll 2.0.50727.832 13-Apr-2007 03:21 802,304
Mscordacwks.dll 2.0.50727.832 13-Apr-2007 03:21 802,304
Mscoree.dll 2.0.50727.832 13-Apr-2007 03:21 271,360
Mscorie.dll 2.0.50727.832 13-Apr-2007 03:21 36,864
Mscorjit.dll 2.0.50727.832 13-Apr-2007 03:21 326,656
Mscorlib.dll 2.0.50727.832 13-Apr-2007 03:21 4,308,992
Mscorpe.dll 2.0.50727.832 13-Apr-2007 03:21 102,912
Mscorsvc.dll 2.0.50727.832 13-Apr-2007 03:21 227,328
Mscorsvw.exe 2.0.50727.832 13-Apr-2007 03:21 68,952
Mscorwks.dll 2.0.50727.832 13-Apr-2007 03:21 5,634,048
Ngen.exe 2.0.50727.832 13-Apr-2007 03:21 99,152
Normalization.dll 2.0.50727.832 13-Apr-2007 03:21 15,360
Normidna.nlp N/A 13-Apr-2007 03:21 59,342
Normnfc.nlp N/A 13-Apr-2007 03:21 45,794
Normnfd.nlp N/A 13-Apr-2007 03:21 39,284
Normnfkc.nlp N/A 13-Apr-2007 03:21 66,384
Normnfkd.nlp N/A 13-Apr-2007 03:21 60,294
Peverify.dll 2.0.50727.832 13-Apr-2007 03:21 136,192
Sos.dll 2.0.50727.832 13-Apr-2007 03:21 382,464
Sysglobl.dll 2.0.50727.832 13-Apr-2007 03:21 110,592
System.configuration.dll 2.0.50727.832 13-Apr-2007 03:21 413,696
System.data.dll 2.0.50727.832 13-Apr-2007 03:21 2,902,016
System.data.oracleclient.dll 2.0.50727.832 13-Apr-2007 03:21 482,304
System.data.sqlxml.dll 2.0.50727.832 13-Apr-2007 03:21 716,800
System.deployment.dll 2.0.50727.832 13-Apr-2007 03:20 888,832
System.design.dll 2.0.50727.832 13-Apr-2007 03:21 5,001,216
System.directoryservices.protocols.dll 2.0.50727.832 13-Apr-2007 03:21 188,416
System.dll 2.0.50727.832 13-Apr-2007 03:21 2,940,928
System.drawing.dll 2.0.50727.832 13-Apr-2007 03:21 577,536
System.enterpriseservices.dll 2.0.50727.832 13-Apr-2007 03:21 258,048
System.enterpriseservices.thunk.dll 2.0.50727.832 13-Apr-2007 03:21 47,616
System.enterpriseservices.tlb 2.0.50727.832 13-Apr-2007 03:21 40,960
System.enterpriseservices.wrapper.dll 2.0.50727.832 13-Apr-2007 03:21 114,176
System.management.dll 2.0.50727.832 13-Apr-2007 03:21 372,736
System.runtime.remoting.dll 2.0.50727.832 13-Apr-2007 03:21 299,008
System.transactions.dll 2.0.50727.832 13-Apr-2007 03:21 260,096
System.web.dll 2.0.50727.832 13-Apr-2007 03:21 5,156,864
System.windows.forms.dll 2.0.50727.832 13-Apr-2007 03:21 5,152,768
System.xml.dll 2.0.50727.832 13-Apr-2007 03:21 2,027,520
Vbc.exe 8.0.50727.832 13-Apr-2007 03:21 1,166,672
Vsavb7rt.dll 8.0.50727.832 13-Apr-2007 03:20 1,330,688
Webadminpage.cs N/A 13-Apr-2007 03:20 48,637
Webengine.dll 2.0.50727.832 13-Apr-2007 03:20 406,016

Microsoft .NET Framework 2.0 (KB928365) (ia64):

File Name Version Date Time Size CPU
Applaunch.exe 2.0.50727.832 12-Apr-2007 23:23 129,880 IA-64
Aspnet.mof N/A 12-Apr-2007 19:19 53,674 N/A
Aspnetmmcext.dll 2.0.50727.832 13-Apr-2007 02:56 507,904 x86
Aspnet_filter.dll 2.0.50727.832 12-Apr-2007 19:26 34,304 IA-64
Aspnet_isapi.dll 2.0.50727.832 12-Apr-2007 19:26 18,944 IA-64
Aspnet_perf.dll 2.0.50727.832 12-Apr-2007 19:26 72,704 IA-64
Aspnet_perf.ini N/A 12-Apr-2007 19:26 777,254 N/A
Aspnet_perf2.ini N/A 12-Apr-2007 19:26 775,658 N/A
Aspnet_rc.dll 2.0.50727.832 12-Apr-2007 19:26 74,752 IA-64
Aspnet_regiis.exe 2.0.50727.832 12-Apr-2007 23:23 79,200 IA-64
Aspnet_state.exe 2.0.50727.832 12-Apr-2007 23:23 92,512 IA-64
Aspnet_state_perf.ini N/A 12-Apr-2007 19:26 42,868 N/A
Aspnet_wp.exe 2.0.50727.832 12-Apr-2007 23:23 83,288 IA-64
Corperfmonext.dll 2.0.50727.832 12-Apr-2007 19:08 191,488 IA-64
Dfsvc.exe 2.0.50727.832 12-Apr-2007 23:23 5,120 x86
Ieexec.exe 2.0.50727.832 12-Apr-2007 23:23 9,728 x86
Ilasm.exe 2.0.50727.832 12-Apr-2007 23:23 675,152 IA-64
Installutil.exe 2.0.50727.832 12-Apr-2007 23:23 24,576 IA-64
Microsoft.build.engine.dll 2.0.50727.832 13-Apr-2007 02:56 413,696 x86
Microsoft.build.tasks.dll 2.0.50727.832 13-Apr-2007 02:56 647,168 x86
Microsoft.common.targets N/A 12-Apr-2007 19:31 177,541 N/A
Microsoft.jscript.dll 8.0.50727.832 13-Apr-2007 02:56 749,568 x86
Mmcaspext.dll 2.0.50727.832 12-Apr-2007 19:27 164,352 IA-64
Mscordacwks.dll 2.0.50727.832 12-Apr-2007 19:17 2,719,232 IA-64
Mscordacwks.dll 2.0.50727.832 12-Apr-2007 19:17 2,719,232 IA-64
Mscoree.dll 2.0.50727.832 12-Apr-2007 19:08 883,200 IA-64
Mscorie.dll 2.0.50727.832 12-Apr-2007 19:13 85,504 IA-64
Mscorjit.dll 2.0.50727.832 12-Apr-2007 19:15 2,706,944 IA-64
Mscorlib.dll 2.0.50727.832 12-Apr-2007 23:23 3,960,832 IA-64
Mscorpe.dll 2.0.50727.832 12-Apr-2007 19:08 313,856 IA-64
Mscorpjt.dll 2.0.50727.832 12-Apr-2007 19:15 3,502,080 IA-64
Mscorsvc.dll 2.0.50727.832 12-Apr-2007 19:14 877,056 IA-64
Mscorsvw.exe 2.0.50727.832 12-Apr-2007 23:23 174,936 IA-64
Mscorwks.dll 2.0.50727.832 12-Apr-2007 19:13 21,324,288 IA-64
Ngen.exe 2.0.50727.832 12-Apr-2007 23:23 247,120 IA-64
Normalization.dll 2.0.50727.832 12-Apr-2007 19:14 44,032 IA-64
Normidna.nlp N/A 12-Apr-2007 19:16 59,342 N/A
Normnfc.nlp N/A 12-Apr-2007 19:16 45,794 N/A
Normnfd.nlp N/A 12-Apr-2007 19:16 39,284 N/A
Normnfkc.nlp N/A 12-Apr-2007 19:16 66,384 N/A
Normnfkd.nlp N/A 12-Apr-2007 19:16 60,294 N/A
Peverify.dll 2.0.50727.832 12-Apr-2007 19:15 383,488 IA-64
Sos.dll 2.0.50727.832 12-Apr-2007 19:25 862,720 IA-64
Sysglobl.dll 2.0.50727.832 13-Apr-2007 02:56 110,592 x86
System.configuration.dll 2.0.50727.832 13-Apr-2007 02:56 413,696 x86
System.data.dll 2.0.50727.832 12-Apr-2007 23:23 3,109,888 IA-64
System.data.oracleclient.dll 2.0.50727.832 12-Apr-2007 23:23 501,760 IA-64
System.data.sqlxml.dll 2.0.50727.832 13-Apr-2007 02:56 716,800 x86
System.deployment.dll 2.0.50727.832 13-Apr-2007 02:56 888,832 x86
System.design.dll 2.0.50727.832 13-Apr-2007 02:56 5,001,216 x86
System.directoryservices.protocols.dll 2.0.50727.832 13-Apr-2007 02:56 188,416 x86
System.dll 2.0.50727.832 13-Apr-2007 02:56 2,940,928 x86
System.drawing.dll 2.0.50727.832 13-Apr-2007 02:56 577,536 x86
System.enterpriseservices.dll 2.0.50727.832 12-Apr-2007 23:23 245,760 IA-64
System.enterpriseservices.thunk.dll 2.0.50727.832 12-Apr-2007 19:16 113,152 IA-64
System.enterpriseservices.tlb 2.0.50727.832 12-Apr-2007 19:25 33,280 N/A
System.enterpriseservices.wrapper.dll 2.0.50727.832 12-Apr-2007 18:48 175,104 IA-64
System.management.dll 2.0.50727.832 13-Apr-2007 02:56 372,736 x86
System.runtime.remoting.dll 2.0.50727.832 13-Apr-2007 02:56 299,008 x86
System.transactions.dll 2.0.50727.832 12-Apr-2007 23:23 310,272 IA-64
System.web.dll 2.0.50727.832 12-Apr-2007 23:23 4,710,400 IA-64
System.windows.forms.dll 2.0.50727.832 13-Apr-2007 02:56 5,152,768 x86
System.xml.dll 2.0.50727.832 13-Apr-2007 02:56 2,027,520 x86
Vbc.exe 8.0.50727.832 12-Apr-2007 23:23 2,997,584 IA-64
Vsavb7rt.dll 8.0.50727.832 13-Apr-2007 03:20 1,330,688 x86
Webadminpage.cs N/A 12-Apr-2007 19:19 48,637 N/A
Webengine.dll 2.0.50727.832 12-Apr-2007 19:26 1,181,696 IA-64
Applaunch.exe 2.0.50727.832 13-Apr-2007 03:21 58,712 x86
Aspnet.mof N/A 13-Apr-2007 03:20 53,674 N/A
Aspnetmmcext.dll 2.0.50727.832 13-Apr-2007 03:20 507,904 x86
Aspnet_filter.dll 2.0.50727.832 13-Apr-2007 03:20 10,752 x86
Aspnet_isapi.dll 2.0.50727.832 13-Apr-2007 03:20 8,192 x86
Aspnet_perf.dll 2.0.50727.832 13-Apr-2007 03:20 23,552 x86
Aspnet_perf.ini N/A 13-Apr-2007 03:20 777,248 N/A
Aspnet_perf2.ini N/A 13-Apr-2007 03:20 775,652 N/A
Aspnet_rc.dll 2.0.50727.832 13-Apr-2007 03:20 75,264 x86
Aspnet_regiis.exe 2.0.50727.832 13-Apr-2007 03:20 32,608 x86
Aspnet_state.exe 2.0.50727.832 13-Apr-2007 03:20 33,632 x86
Aspnet_state_perf.ini N/A 13-Apr-2007 03:20 42,868 N/A
Aspnet_wp.exe 2.0.50727.832 13-Apr-2007 03:20 32,600 x86
Corperfmonext.dll 2.0.50727.832 13-Apr-2007 03:21 88,576 x86
Dfsvc.exe 2.0.50727.832 13-Apr-2007 03:20 5,120 x86
Ieexec.exe 2.0.50727.832 13-Apr-2007 03:21 9,728 x86
Ilasm.exe 2.0.50727.832 13-Apr-2007 03:21 228,688 x86
Installutil.exe 2.0.50727.832 13-Apr-2007 03:21 28,672 x86
Microsoft.build.engine.dll 2.0.50727.832 13-Apr-2007 03:21 413,696 x86
Microsoft.build.tasks.dll 2.0.50727.832 13-Apr-2007 03:21 647,168 x86
Microsoft.common.targets N/A 13-Apr-2007 03:21 177,541 N/A
Microsoft.jscript.dll 8.0.50727.832 13-Apr-2007 03:21 749,568 x86
Mmcaspext.dll 2.0.50727.832 13-Apr-2007 03:20 87,040 x86
Mscordacwks.dll 2.0.50727.832 13-Apr-2007 03:21 802,304 x86
Mscordacwks.dll 2.0.50727.832 13-Apr-2007 03:21 802,304 x86
Mscoree.dll 2.0.50727.832 13-Apr-2007 03:21 271,360 x86
Mscorie.dll 2.0.50727.832 13-Apr-2007 03:21 36,864 x86
Mscorjit.dll 2.0.50727.832 13-Apr-2007 03:21 326,656 x86
Mscorlib.dll 2.0.50727.832 13-Apr-2007 03:21 4,308,992 x86
Mscorpe.dll 2.0.50727.832 13-Apr-2007 03:21 102,912 x86
Mscorsvc.dll 2.0.50727.832 13-Apr-2007 03:21 227,328 x86
Mscorsvw.exe 2.0.50727.832 13-Apr-2007 03:21 68,952 x86
Mscorwks.dll 2.0.50727.832 13-Apr-2007 03:21 5,634,048 x86
Ngen.exe 2.0.50727.832 13-Apr-2007 03:21 99,152 x86
Normalization.dll 2.0.50727.832 13-Apr-2007 03:21 15,360 x86
Normidna.nlp N/A 13-Apr-2007 03:21 59,342 N/A
Normnfc.nlp N/A 13-Apr-2007 03:21 45,794 N/A
Normnfd.nlp N/A 13-Apr-2007 03:21 39,284 N/A
Normnfkc.nlp N/A 13-Apr-2007 03:21 66,384 N/A
Normnfkd.nlp N/A 13-Apr-2007 03:21 60,294 N/A
Peverify.dll 2.0.50727.832 13-Apr-2007 03:21 136,192 x86
Sos.dll 2.0.50727.832 13-Apr-2007 03:21 382,464 x86
Sysglobl.dll 2.0.50727.832 13-Apr-2007 03:21 110,592 x86
System.configuration.dll 2.0.50727.832 13-Apr-2007 03:21 413,696 x86
System.data.dll 2.0.50727.832 13-Apr-2007 03:21 2,902,016 x86
System.data.oracleclient.dll 2.0.50727.832 13-Apr-2007 03:21 482,304 x86
System.data.sqlxml.dll 2.0.50727.832 13-Apr-2007 03:21 716,800 x86
System.deployment.dll 2.0.50727.832 13-Apr-2007 03:20 888,832 x86
System.design.dll 2.0.50727.832 13-Apr-2007 03:21 5,001,216 x86
System.directoryservices.protocols.dll 2.0.50727.832 13-Apr-2007 03:21 188,416 x86
System.dll 2.0.50727.832 13-Apr-2007 03:21 2,940,928 x86
System.drawing.dll 2.0.50727.832 13-Apr-2007 03:21 577,536 x86
System.enterpriseservices.dll 2.0.50727.832 13-Apr-2007 03:21 258,048 x86
System.enterpriseservices.thunk.dll 2.0.50727.832 13-Apr-2007 03:21 47,616 x86
System.enterpriseservices.tlb 2.0.50727.832 13-Apr-2007 03:21 40,960 N/A
System.enterpriseservices.wrapper.dll 2.0.50727.832 13-Apr-2007 03:21 114,176 x86
System.management.dll 2.0.50727.832 13-Apr-2007 03:21 372,736 x86
System.runtime.remoting.dll 2.0.50727.832 13-Apr-2007 03:21 299,008 x86
System.transactions.dll 2.0.50727.832 13-Apr-2007 03:21 260,096 x86
System.web.dll 2.0.50727.832 13-Apr-2007 03:21 5,156,864 x86
System.windows.forms.dll 2.0.50727.832 13-Apr-2007 03:21 5,152,768 x86
System.xml.dll 2.0.50727.832 13-Apr-2007 03:21 2,027,520 x86
Vbc.exe 8.0.50727.832 13-Apr-2007 03:21 1,166,672 x86
Webadminpage.cs N/A 13-Apr-2007 03:20 48,637 N/A
Webengine.dll 2.0.50727.832 13-Apr-2007 03:20 406,016 x86

Microsoft .NET Framework 2.0 (KB928365) (x64):

File Name Version Date Time Size CPU
Applaunch.exe 2.0.50727.832 12-Apr-2007 22:33 73,048 x64
Aspnet.mof N/A 12-Apr-2007 19:17 53,674 N/A
Aspnetmmcext.dll 2.0.50727.832 13-Apr-2007 02:56 507,904 x86
Aspnet_filter.dll 2.0.50727.832 12-Apr-2007 19:23 13,312 x64
Aspnet_isapi.dll 2.0.50727.832 12-Apr-2007 19:23 10,240 x64
Aspnet_perf.dll 2.0.50727.832 12-Apr-2007 19:23 32,256 x64
Aspnet_perf.ini N/A 12-Apr-2007 19:23 777,254 N/A
Aspnet_perf2.ini N/A 12-Apr-2007 19:23 775,658 N/A
Aspnet_rc.dll 2.0.50727.832 12-Apr-2007 19:23 74,752 x64
Aspnet_regiis.exe 2.0.50727.832 12-Apr-2007 22:33 46,944 x64
Aspnet_state.exe 2.0.50727.832 12-Apr-2007 22:33 45,920 x64
Aspnet_state_perf.ini N/A 12-Apr-2007 19:23 42,868 N/A
Aspnet_wp.exe 2.0.50727.832 12-Apr-2007 22:33 44,376 x64
Corperfmonext.dll 2.0.50727.832 12-Apr-2007 19:08 101,888 x64
Dfsvc.exe 2.0.50727.832 12-Apr-2007 22:33 5,120 x86
Ieexec.exe 2.0.50727.832 12-Apr-2007 22:33 9,728 x86
Ilasm.exe 2.0.50727.832 12-Apr-2007 22:33 333,648 x64
Installutil.exe 2.0.50727.832 12-Apr-2007 22:33 24,576 x64
Microsoft.build.engine.dll 2.0.50727.832 13-Apr-2007 02:56 413,696 x86
Microsoft.build.tasks.dll 2.0.50727.832 13-Apr-2007 02:56 647,168 x86
Microsoft.common.targets N/A 12-Apr-2007 19:28 177,541 N/A
Microsoft.jscript.dll 8.0.50727.832 13-Apr-2007 02:56 749,568 x86
Mmcaspext.dll 2.0.50727.832 12-Apr-2007 19:23 105,984 x64
Mscordacwks.dll 2.0.50727.832 12-Apr-2007 19:15 1,597,440 x64
Mscordacwks.dll 2.0.50727.832 12-Apr-2007 19:15 1,597,440 x64
Mscoree.dll 2.0.50727.832 12-Apr-2007 19:08 457,216 x64
Mscorie.dll 2.0.50727.832 12-Apr-2007 19:12 31,232 x64
Mscorjit.dll 2.0.50727.832 12-Apr-2007 19:13 1,588,224 x64
Mscorlib.dll 2.0.50727.832 12-Apr-2007 22:33 3,960,832 x64
Mscorpe.dll 2.0.50727.832 12-Apr-2007 19:08 157,184 x64
Mscorpjt.dll 2.0.50727.832 12-Apr-2007 19:14 2,006,016 x64
Mscorsvc.dll 2.0.50727.832 12-Apr-2007 19:12 516,608 x64
Mscorsvw.exe 2.0.50727.832 12-Apr-2007 22:33 93,016 x64
Mscorwks.dll 2.0.50727.832 12-Apr-2007 19:11 10,335,744 x64
Ngen.exe 2.0.50727.832 12-Apr-2007 22:33 166,736 x64
Normalization.dll 2.0.50727.832 12-Apr-2007 19:12 18,432 x64
Normidna.nlp N/A 12-Apr-2007 19:14 59,342 N/A
Normnfc.nlp N/A 12-Apr-2007 19:14 45,794 N/A
Normnfd.nlp N/A 12-Apr-2007 19:14 39,284 N/A
Normnfkc.nlp N/A 12-Apr-2007 19:14 66,384 N/A
Normnfkd.nlp N/A 12-Apr-2007 19:14 60,294 N/A
Peverify.dll 2.0.50727.832 12-Apr-2007 19:13 205,824 x64
Sos.dll 2.0.50727.832 12-Apr-2007 19:22 480,768 x64
Sysglobl.dll 2.0.50727.832 13-Apr-2007 02:56 110,592 x86
System.configuration.dll 2.0.50727.832 13-Apr-2007 02:56 413,696 x86
System.data.dll 2.0.50727.832 12-Apr-2007 22:33 2,967,040 x64
System.data.oracleclient.dll 2.0.50727.832 12-Apr-2007 22:33 498,688 x64
System.data.sqlxml.dll 2.0.50727.832 13-Apr-2007 02:56 716,800 x86
System.deployment.dll 2.0.50727.832 13-Apr-2007 02:56 888,832 x86
System.design.dll 2.0.50727.832 13-Apr-2007 02:56 5,001,216 x86
System.directoryservices.protocols.dll 2.0.50727.832 13-Apr-2007 02:56 188,416 x86
System.dll 2.0.50727.832 13-Apr-2007 02:56 2,940,928 x86
System.drawing.dll 2.0.50727.832 13-Apr-2007 02:56 577,536 x86
System.enterpriseservices.dll 2.0.50727.832 12-Apr-2007 22:33 245,760 x64
System.enterpriseservices.thunk.dll 2.0.50727.832 12-Apr-2007 19:14 55,296 x64
System.enterpriseservices.tlb 2.0.50727.832 12-Apr-2007 19:22 33,280 N/A
System.enterpriseservices.wrapper.dll 2.0.50727.832 12-Apr-2007 18:46 132,608 x64
System.management.dll 2.0.50727.832 13-Apr-2007 02:56 372,736 x86
System.runtime.remoting.dll 2.0.50727.832 13-Apr-2007 02:56 299,008 x86
System.transactions.dll 2.0.50727.832 12-Apr-2007 22:33 282,624 x64
System.web.dll 2.0.50727.832 12-Apr-2007 22:33 5,087,232 x64
System.windows.forms.dll 2.0.50727.832 13-Apr-2007 02:56 5,152,768 x86
System.xml.dll 2.0.50727.832 13-Apr-2007 02:56 2,027,520 x86
Vbc.exe 8.0.50727.832 12-Apr-2007 22:33 1,803,600 x64
Vsavb7rt.dll 8.0.50727.832 13-Apr-2007 03:20 1,330,688 x86
Webadminpage.cs N/A 12-Apr-2007 19:17 48,637 N/A
Webengine.dll 2.0.50727.832 12-Apr-2007 19:23 710,144 x64
Applaunch.exe 2.0.50727.832 13-Apr-2007 03:21 58,712 x86
Aspnet.mof N/A 13-Apr-2007 03:20 53,674 N/A
Aspnetmmcext.dll 2.0.50727.832 13-Apr-2007 03:20 507,904 x86
Aspnet_filter.dll 2.0.50727.832 13-Apr-2007 03:20 10,752 x86
Aspnet_isapi.dll 2.0.50727.832 13-Apr-2007 03:20 8,192 x86
Aspnet_perf.dll 2.0.50727.832 13-Apr-2007 03:20 23,552 x86
Aspnet_perf.ini N/A 13-Apr-2007 03:20 777,248 N/A
Aspnet_perf2.ini N/A 13-Apr-2007 03:20 775,652 N/A
Aspnet_rc.dll 2.0.50727.832 13-Apr-2007 03:20 75,264 x86
Aspnet_regiis.exe 2.0.50727.832 13-Apr-2007 03:20 32,608 x86
Aspnet_state.exe 2.0.50727.832 13-Apr-2007 03:20 33,632 x86
Aspnet_state_perf.ini N/A 13-Apr-2007 03:20 42,868 N/A
Aspnet_wp.exe 2.0.50727.832 13-Apr-2007 03:20 32,600 x86
Corperfmonext.dll 2.0.50727.832 13-Apr-2007 03:21 88,576 x86
Dfsvc.exe 2.0.50727.832 13-Apr-2007 03:20 5,120 x86
Ieexec.exe 2.0.50727.832 13-Apr-2007 03:21 9,728 x86
Ilasm.exe 2.0.50727.832 13-Apr-2007 03:21 228,688 x86
Installutil.exe 2.0.50727.832 13-Apr-2007 03:21 28,672 x86
Microsoft.build.engine.dll 2.0.50727.832 13-Apr-2007 03:21 413,696 x86
Microsoft.build.tasks.dll 2.0.50727.832 13-Apr-2007 03:21 647,168 x86
Microsoft.common.targets N/A 13-Apr-2007 03:21 177,541 N/A
Microsoft.jscript.dll 8.0.50727.832 13-Apr-2007 03:21 749,568 x86
Mmcaspext.dll 2.0.50727.832 13-Apr-2007 03:20 87,040 x86
Mscordacwks.dll 2.0.50727.832 13-Apr-2007 03:21 802,304 x86
Mscordacwks.dll 2.0.50727.832 13-Apr-2007 03:21 802,304 x86
Mscoree.dll 2.0.50727.832 13-Apr-2007 03:21 271,360 x86
Mscorie.dll 2.0.50727.832 13-Apr-2007 03:21 36,864 x86
Mscorjit.dll 2.0.50727.832 13-Apr-2007 03:21 326,656 x86
Mscorlib.dll 2.0.50727.832 13-Apr-2007 03:21 4,308,992 x86
Mscorpe.dll 2.0.50727.832 13-Apr-2007 03:21 102,912 x86
Mscorsvc.dll 2.0.50727.832 13-Apr-2007 03:21 227,328 x86
Mscorsvw.exe 2.0.50727.832 13-Apr-2007 03:21 68,952 x86
Mscorwks.dll 2.0.50727.832 13-Apr-2007 03:21 5,634,048 x86
Ngen.exe 2.0.50727.832 13-Apr-2007 03:21 99,152 x86
Normalization.dll 2.0.50727.832 13-Apr-2007 03:21 15,360 x86
Normidna.nlp N/A 13-Apr-2007 03:21 59,342 N/A
Normnfc.nlp N/A 13-Apr-2007 03:21 45,794 N/A
Normnfd.nlp N/A 13-Apr-2007 03:21 39,284 N/A
Normnfkc.nlp N/A 13-Apr-2007 03:21 66,384 N/A
Normnfkd.nlp N/A 13-Apr-2007 03:21 60,294 N/A
Peverify.dll 2.0.50727.832 13-Apr-2007 03:21 136,192 x86
Sos.dll 2.0.50727.832 13-Apr-2007 03:21 382,464 x86
Sysglobl.dll 2.0.50727.832 13-Apr-2007 03:21 110,592 x86
System.configuration.dll 2.0.50727.832 13-Apr-2007 03:21 413,696 x86
System.data.dll 2.0.50727.832 13-Apr-2007 03:21 2,902,016 x86
System.data.oracleclient.dll 2.0.50727.832 13-Apr-2007 03:21 482,304 x86
System.data.sqlxml.dll 2.0.50727.832 13-Apr-2007 03:21 716,800 x86
System.deployment.dll 2.0.50727.832 13-Apr-2007 03:20 888,832 x86
System.design.dll 2.0.50727.832 13-Apr-2007 03:21 5,001,216 x86
System.directoryservices.protocols.dll 2.0.50727.832 13-Apr-2007 03:21 188,416 x86
System.dll 2.0.50727.832 13-Apr-2007 03:21 2,940,928 x86
System.drawing.dll 2.0.50727.832 13-Apr-2007 03:21 577,536 x86
System.enterpriseservices.dll 2.0.50727.832 13-Apr-2007 03:21 258,048 x86
System.enterpriseservices.thunk.dll 2.0.50727.832 13-Apr-2007 03:21 47,616 x86
System.enterpriseservices.tlb 2.0.50727.832 13-Apr-2007 03:21 40,960 N/A
System.enterpriseservices.wrapper.dll 2.0.50727.832 13-Apr-2007 03:21 114,176 x86
System.management.dll 2.0.50727.832 13-Apr-2007 03:21 372,736 x86
System.runtime.remoting.dll 2.0.50727.832 13-Apr-2007 03:21 299,008 x86
System.transactions.dll 2.0.50727.832 13-Apr-2007 03:21 260,096 x86
System.web.dll 2.0.50727.832 13-Apr-2007 03:21 5,156,864 x86
System.windows.forms.dll 2.0.50727.832 13-Apr-2007 03:21 5,152,768 x86
System.xml.dll 2.0.50727.832 13-Apr-2007 03:21 2,027,520 x86
Vbc.exe 8.0.50727.832 13-Apr-2007 03:21 1,166,672 x86
Webadminpage.cs N/A 13-Apr-2007 03:20 48,637 N/A
Webengine.dll 2.0.50727.832 13-Apr-2007 03:20 406,016 x86

Microsoft .NET Framework 2.0 (KB929916):

File Name Version Date Time Size
Aspnet_isapi.dll 2.0.50727.833 14-Apr-2007 03:24 8,192
Aspnet_regiis.exe 2.0.50727.833 14-Apr-2007 03:24 32,608
Aspnet_wp.exe 2.0.50727.833 14-Apr-2007 03:24 32,600
System.web.dll 2.0.50727.833 14-Apr-2007 03:25 5,156,864
Vsavb7rt.dll 8.0.50727.833 14-Apr-2007 03:24 1,330,688
Webengine.dll 2.0.50727.833 14-Apr-2007 03:24 406,016

Microsoft .NET Framework 2.0 (KB929916) (x64):

File Name Version Date Time Size CPU
Aspnet_isapi.dll 2.0.50727.833 13-Apr-2007 19:24 10,240 x64
Aspnet_regiis.exe 2.0.50727.833 13-Apr-2007 22:33 46,944 x64
Aspnet_wp.exe 2.0.50727.833 13-Apr-2007 22:33 44,376 x64
System.web.dll 2.0.50727.833 13-Apr-2007 22:33 5,087,232 x64
Vsavb7rt.dll 8.0.50727.833 14-Apr-2007 03:24 1,330,688 x86
Webengine.dll 2.0.50727.833 13-Apr-2007 19:24 710,144 x64
Aspnet_isapi.dll 2.0.50727.833 14-Apr-2007 03:24 8,192 x86
Aspnet_regiis.exe 2.0.50727.833 14-Apr-2007 03:24 32,608 x86
Aspnet_wp.exe 2.0.50727.833 14-Apr-2007 03:24 32,600 x86
System.web.dll 2.0.50727.833 14-Apr-2007 03:25 5,156,864 x86
Webengine.dll 2.0.50727.833 14-Apr-2007 03:24 406,016 x86

Deployment Information

Installing the Update

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.

Microsoft .NET Framework 2.0 (KB928365):

Supported Security Update Installation Switches
Switch Description
/?, /h, /help Displays the command-line options.
Setup Mode
/q[n|b|r|f] Sets user interface level
n – No UI b - Basic UI r - Reduced UI f - Full UI (default).
Install Options
/extract [directory] Extract the package to the specified directory.
Restart Options
/norestart Do not restart after the installation is complete
/promptrestart Prompts the user for restart if necessary
/forcerestart Always restart the computer after installation
Logging Options
/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile> i - Status messages
w - Nonfatal warnings e - All error messages a - Start up of actions r - Action-specific records u - User requests c - Initial UI parameters m - Out-of-memory or fatal exit information o - Out-of-disk-space messages p - Terminal properties v - Verbose output x - Extra debugging information + - Append to existing log file ! - Flush each line to the log * - Log all information, except for v and x options
/log <LogFile> Equivalent of /l* <LogFile>

Microsoft .NET Framework 2.0 (KB929916):

Switch Description
/?, /h, /help Displays help on supported switches.
/quiet Suppresses the display of status or error messages.
/norestart When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.

Removal Information To remove this update, use the Add or Remove Programs tool in Control Panel.

Verifying Update Installation

  • 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 of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

      Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.

    5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.

      Note Attributes other than 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 the update installation. 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:

  • Dinis Cruz of OWASP for reporting the .NET PE Loader Vulnerability (CVE-2007-0041).
  • Paul Craig of Security Assessment for reporting the ASP.NET Null Byte Termination Vulnerability (CVE-2007-0042).
  • Jeroen Frijters of Sumatra for reporting the .NET JIT Compiler Vulnerability (CVE-2007-0043).
  • ProCheckUp working with UK CPNI for originally reporting the .NET Request Filtering Bypass Vulnerability (CVE-2006-7192).
  • Ferruh T. Mavituna of Portcullis Computer Security Ltd. for working with Microsoft and supplying additional information about the .NET Request Filtering Bypass Vulnerability (CVE-2006-7192).
  • Johannes Gumbel of TrueSec for working with Microsoft and supplying additional information about the .NET Request Filtering Bypass Vulnerability (CVE-2006-7192).

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 (July 10, 2007): Bulletin published.
  • V1.1 (July 12, 2007): Bulletin updated: Corrected Windows Vista severity rating in the “Affected Software” table to Important. Corrected several instances in the file manifest tables incorrectly referencing a version of Mscordacwks.dll that is not installed on the system. Added an additional FAQ explaining why customers installing .NET Framework 3.0 should update .NET Framework 2.0 on their system. Added an additional FAQ for ASP.NET Web application developers.
  • V1.2 (July 19, 2007): Bulletin updated: Corrected KB933854 file manifest table for .NET Framework 1.1 on supported versions of Windows Server 2003. The Bulletin has also been updated providing an additional link to the main Bulletin Knowledge Base Article which will document all non-security functionality changes introduced in this .NET Framework security update.
  • V1.3 (July 25, 2007): Bulletin updated: Additional clarification has been added to the Bulletin explaining that .NET Framework updates are cumulative and may contain non-security updates. The Bulletin was also updated to clarify that this update applies to Service Pack 3 for .NET Framework 1.0 and Service pack 1 for .NET Framework 1.1.
  • V2.0 (March 25, 2008): Bulletin updated: Added .NET Framework 1.0 (KB928367) and .NET Framework 1.1 (KB929729) as affected components for Windows Vista Service Pack 1 and Windows Server 2008.
  • V3.0 (April 22, 2008): Bulletin updated: Added .NET Framework 1.0 (KB928367), .NET Framework 1.1 (KB928366), and .NET Framework Version 2.0 (KB928365) as affected components for Windows XP Service Pack 3. This is a detection update only. There were no changes to the binaries.
  • V3.1 (April 23, 2008): Bulletin updated: Removed erroneous references to Windows XP Professional x64 Edition Service Pack 3.
  • V3.2 (May 7, 2008): Bulletin updated: Removed erroneous references to .NET Framework 1.0 as a component of Windows Server 2008 x64 Edition and Windows Server 2008 for Itanium-based Systems.
  • V4.0 (May 7, 2009): Bulletin updated: Added as affected software: Microsoft .NET Framework 1.0 (KB928367) on 32-bit and x64-based editions of Windows Vista Service Pack 2 and on 32-bit editions of Windows Server 2008 Service Pack 2; Microsoft .NET Framework 1.1 (KB929729) on 32-bit and x64-based editions of Windows Vista Service Pack 2 and on 32-bit, x64-based, and Itanium-based editions of Windows Server 2008 Service Pack 2. This is a detection change only; there were no changes to the binaries. Customers who have already successfully installed KB928367 or KB929729 do not need to reinstall.

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