Version: 3.2
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.
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 | Remote Code Execution | Critical | |
Windows XP Service Pack 2 and Windows XP Service Pack 3 | Microsoft .NET Framework 1.0 | Remote Code Execution | Critical | |
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Microsoft .NET Framework 1.0 | Remote Code Execution | Critical | |
Windows XP Tablet PC Edition 2005 and Windows XP Media Center Edition 2005 | Microsoft .NET Framework 1.0 | Remote Code Execution | Critical | |
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Microsoft .NET Framework 1.0 | Remote Code Execution | Important | |
Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | Microsoft .NET Framework 1.0 | Remote Code Execution | Important | |
Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Microsoft .NET Framework 1.0 | Remote Code Execution | Important | |
Windows Vista and Windows Vista Service Pack 1 | Microsoft .NET Framework 1.0 | Information Disclosure | Important | |
Windows Server 2008 | Microsoft .NET Framework 1.0 | Information Disclosure | Important | None |
| Microsoft .NET Framework 1.1 Service Pack 1 | ||||
Windows 2000 Service Pack 4 | Microsoft .NET Framework 1.1 | Remote Code Execution | Critical | |
Windows XP Service Pack 2 and Windows XP Service Pack 3 | Microsoft .NET Framework 1.1 | Remote Code Execution | Critical | |
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Microsoft .NET Framework 1.1 | Remote Code Execution | Critical | |
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Microsoft .NET Framework 1.1 | Remote Code Execution | Important | |
Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | Microsoft .NET Framework 1.1 | Remote Code Execution | Important | |
Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Microsoft .NET Framework 1.1 | Remote Code Execution | Important | |
Windows Vista and Windows Vista Service Pack 1 | Microsoft .NET Framework 1.1 | Information Disclosure | Important | |
Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1 | Microsoft .NET Framework 1.1 | Information Disclosure | Important | |
Windows Server 2008 | Microsoft .NET Framework 1.1 | Information Disclosure | Important | None |
Windows Server 2008 for Itanium-based Systems | Microsoft .NET Framework 1.1 | Information Disclosure | Important | None |
Windows Server 2008 x64 Edition | Microsoft .NET Framework 1.1 | Information Disclosure | Important | None |
| Microsoft .NET Framework 2.0 | ||||
Windows 2000 Service Pack 4 | Microsoft .NET Framework 2.0 | Remote Code Execution | Critical | |
Windows XP Service Pack 2 and Windows XP Service Pack 3 | Microsoft .NET Framework 2.0 | Remote Code Execution | Critical | |
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Microsoft .NET Framework 2.0 | Remote Code Execution | Critical | |
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Microsoft .NET Framework 2.0 | Remote Code Execution | Important | |
Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | Microsoft .NET Framework 2.0 | Remote Code Execution | Important | |
Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Microsoft .NET Framework 2.0 | Remote Code Execution | Important | |
Windows Vista | Microsoft .NET Framework 2.0 | Information Disclosure | Important | None |
Windows Vista x64 Edition | Microsoft .NET Framework 2.0 | 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 and Microsoft .NET Framework 3.0 Service Pack 1 |
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Microsoft .NET Framework 3.0 and Microsoft .NET Framework 3.0 Service Pack 1 |
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Microsoft .NET Framework 3.0 and Microsoft .NET Framework 3.0 Service Pack 1 |
Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Microsoft .NET Framework 3.0 and Microsoft .NET Framework 3.0 Service Pack 1 |
Windows Vista | Microsoft .NET Framework 3.0 |
Windows Vista x64 Edition | Microsoft .NET Framework 3.0 |
Windows Vista Service Pack 1 | Microsoft .NET Framework 2.0 Service Pack 1 and Microsoft .NET Framework 3.0 Service Pack 1 |
Windows Vista x64 Edition Service Pack 1 | Microsoft .NET Framework 2.0 Service Pack 1 and Microsoft .NET Framework 3.0 Service Pack 1 |
Windows Server 2008 | Microsoft .NET Framework 2.0 Service Pack 1 and Microsoft .NET Framework 3.0 Service Pack 1 |
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.
Frequently Asked Questions (FAQ) Related to This Security Update |
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.
Additional information on the .NET Framework versions and their supported service packs can be found at the following Lifecycle Supported Service Packs support page.
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?
Theaffected 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.
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 and Windows Vista Service Pack 1 | None | Important Information Disclosure | None | Important |
Microsoft .NET Framework 1.1 Service Pack 1 when installed on Windows Vista and Windows Vista Service Pack 1 | None | Important Information Disclosure | None | Important |
Microsoft .NET Framework 1.1 Service Pack 1 when installed on Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1 | 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 | Moderate Remote Code Execution | Important Information Disclosure | None | Important |
Microsoft .NET Framework 1.1 Service Pack 1 when installed on Windows Server 2008 | 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:
| ||||
| • | .NET Framework 1.1 is not included in supported editions of Windows with the exception of the following:
| ||||
| • | .NET Framework 2.0 is not included in supported editions of Windows with the exception of the following:
|
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:
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:
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:
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:
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:
| ||||||||||||||||||||||||||||
| • | 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:
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:
| ||||
| • | .NET Framework 1.1 is not included in supported editions of Windows with the exception of the following:
| ||||
| • | .NET Framework 2.0 is not included in supported editions of Windows with the exception of the following:
|
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:
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:
|
| • | 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:
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:
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:
|
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.
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): |
| Microsoft .NET Framework 1.0 (KB930494): |
Installing without restarting | Microsoft .NET Framework 1.0 (KB928367): |
| Microsoft .NET Framework 1.0 (KB930494): |
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): |
| Microsoft .NET Framework 1.0 (KB930494): |
File Information | See the subsection, File Information, in this section for the full file manifest |
Registry Key Verification | Microsoft .NET Framework 1.0 (KB928367): |
| Microsoft .NET Framework 1.0 (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 |