Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Microsoft Security Bulletin MS06-056 - Moderate

Vulnerability in ASP.NET 2.0 Could Allow Information Disclosure (922770)

Published: October 10, 2006 | Updated: November 29, 2006

Version: 1.3

Summary

Who Should Read this Document: Customers who use Microsoft Windows .NET Framework 2.0

Impact of Vulnerability: Information Disclosure

Maximum Severity Rating: Moderate

Recommendation: Customers should consider applying the security update

Security Update Replacement: None

Caveats: Microsoft Knowledge Base Article 922770 documents the currently known issues that customers may experience when they install this security update. The article also documents recommended solutions for these issues. For more information, see Microsoft Knowledge Base Article 922770.

Tested Software and Security Update Download Locations:

Affected Software:

Microsoft .NET Framework 2.0 for the following operating system versions: Download the update

  • Microsoft Windows 2000 Service Pack 4
  • Microsoft Windows XP Service Pack 1 or Windows XP Service Pack 2
  • Microsoft Windows XP Professional x64 Edition
  • Microsoft Windows XP Tablet PC Edition
  • Microsoft Windows XP Media Center Edition
  • Microsoft Windows Server 2003 or Microsoft Windows Server 2003 Service Pack 1
  • Windows Server 2003 with Service Pack 1 for Itanium-based Systems
  • Microsoft Windows Server 2003 x64 Edition

Non-Affected Software:

  • Microsoft Windows Server 2003 for Itanium-based Systems

Tested Microsoft Windows Components:

Affected Components:

  • Microsoft .NET Framework 2.0

Non-Affected Components:

  • Microsoft .NET Framework 1.0
  • Microsoft .NET Framework 1.1

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.

Note The security updates for Microsoft Windows Server 2003, Windows Server 2003 Service Pack 1, and Windows Server 2003 x64 Edition also apply to Windows Server 2003 R2.

General Information

Executive Summary:

This update resolves a newly discovered, privately reported vulnerability. The vulnerability is documented in the "Vulnerability Details" section of this bulletin.

The vulnerability could allow an attacker to gain unauthorized access to information. Note that this vulnerability would not allow an attacker to execute code to elevate their user rights directly, but it could be used to acquire information that could be used to further compromise the affected system.

We recommend that customers consider applying the security update.

Severity Ratings and Vulnerability Identifiers:

Vulnerability IdentifiersImpact of Vulnerability.NET Framework 2.0
.NET Framework 2.0 Cross-Site Scripting Vulnerability - CVE-2006-3436Information DisclosureModerate

Why is Microsoft Windows Server 2003 for Itanium-based Systems listed in the “Non-Affected Software” section?
Microsoft .NET Framework 2.0 does not install on Microsoft Windows Server 2003 for Itanium-based systems.

Why does Microsoft .NET Framework 2.0 does not install on Microsoft Windows Server 2003 for Itanium-based systems?
Windows Installer 3.1 is not supported on Microsoft Windows Server 2003 for Itanium-based systems. Windows Installer 3.1 is only supported on Windows Server 2003 with Service Pack 1 for Itanium-based systems.

What are the known issues that customers may experience when they install this security update?

Microsoft Knowledge Base Article 922770documents the currently known issues that customers may experience when they install this security update. The article also documents recommended solutions for these issues. For more information, see Microsoft Knowledge Base Article 922770.

Extended security update support for Microsoft Windows NT Workstation 4.0 Service Pack 6a and Windows 2000 Service Pack 2 ended on June 30, 2004. Extended security update support for Microsoft Windows NT Server 4.0 Service Pack 6a ended on December 31, 2004. Extended security update support for Microsoft Windows 2000 Service Pack 3 ended on June 30, 2005. I am still using one of these operating systems, what should I do?
Windows NT Workstation 4.0 Service Pack 6a, Windows NT Server 4.0 Service Pack 6a, Windows 2000 Service Pack 2, and Windows 2000 Service Pack 3 have reached the end of their life cycles. It should be a priority for customers who have these operating system versions 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 Web site. 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 these products 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.

Can I use the Microsoft Baseline Security Analyzer (MBSA) to determine whether this update is required?

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

ProductMBSA 1.2.1Enterprise Update Scan Tool (EST)MBSA 2.0
.NET Framework 2.0 NoYesYes

For more information about MBSA, visit the MBSA Web site. For more information about the programs that Microsoft Update and MBSA 2.0 currently do not detect, see Microsoft Knowledge Base Article 895660.

For more detailed information, see Microsoft Knowledge Base Article 910723.

What is the Enterprise Update Scan Tool (EST)?
As part of an ongoing commitment to provide detection tools for bulletin-class security updates, Microsoft delivers a stand-alone detection tool whenever the Microsoft Baseline Security Analyzer (MBSA) and the Office Detection Tool (ODT) cannot detect whether the update is required for an MSRC release cycle. This stand-alone tool is called the Enterprise Update Scan Tool (EST) and is designed for enterprise administrators. When a version of the Enterprise Update Scan Tool is created for a specific bulletin, customers can run the tool from a command-line interface (CLI) and view the results of the XML output file. To help customers better utilize the tool, detailed documentation will be provided with the tool. There is also a version of the tool that offers an integrated experience for SMS administrators.

Can I use a version of the Enterprise Update Scan Tool (EST) to determine whether this update is required?
Yes. Microsoft has created a version of EST that will determine if you have to apply this update. For download links and more information about the version of the EST that is being released this month, see Microsoft Knowledge Base Article 894193. SMS customers should review the FAQ, “Can I use Systems Management Server (SMS) to determine whether this update is required?" for more information about SMS and EST.

Can I use Systems Management Server (SMS) to determine whether this update is required?
The following table provides the SMS detection summary for this security update.

ProductSMS 2.0SMS 2003
.NET Framework 2.0 Yes (with the EST)Yes

SMS uses MBSA for detection. Therefore, SMS has the same limitation that is listed earlier in this bulletin related to programs that MBSA does not detect.

For SMS 2.0, the SMS SUS Feature Pack, which includes the Security Update Inventory Tool, can be used by SMS to detect security updates. SMS SUIT uses the MBSA 1.2.1 engine for detection. For more information about the Security Update Inventory Tool, visit the following Microsoft Web site. For more information about the limitations of the Security Update Inventory Tool, 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 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 Inventory Tool for Microsoft Updates, visit the following Microsoft Web site. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.

For more information about SMS, visit the SMS Web site.

For more detailed information, see Microsoft Knowledge Base Article 910723.

.NET Framework 2.0 Cross-Site Scripting Vulnerability - CVE-2006-3436:

A cross-site scripting vulnerability exists in a server running a vulnerable version of the .Net Framework 2.0 that could inject a client side script in the user's browser. The script could spoof content, disclose information, or take any action that the user could take on the affected web site. Attempts to exploit this vulnerability require user interaction.

Mitigating Factors for .NET Framework 2.0 Cross-Site Scripting Vulnerability - CVE-2006-3436:

  • In a Web-based attack scenario a compromised Web server an attacker could inject a client side script in the user's browser. The script could spoof content, disclose information, or take any action that the user could take on the affected web site. Attempts to exploit this vulnerability would require user interaction.
  • By default, .NET Framework 2.0 controls do not set the AutoPostBack property to “true”.

Workarounds for .NET Framework 2.0 Cross-Site Scripting Vulnerability - CVE-2006-3436:

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.

  • On computers running .NET Framework 2.0, do not set the AutoPostBack property for controls on a page to “true”:
    • On computers running .NET Framework 2.0 AutoPostBack is a property of controls on a WebForm. By default the AutoPostBack property is set to false. For more information, seeKnowledge Base Article 328923.

FAQ for .NET Framework 2.0 Cross-Site Scripting Vulnerability - CVE-2006-3436:

What is the scope of the vulnerability?
A cross-site scripting vulnerability may exist in a server running a vulnerable version of the .Net Framework 2.0 that could inject a client side script in the user's browser. The vulnerability is within ASP.NET controls that set the AutoPostBack property to “true”. In a Web-based attack scenario a compromised Web site could accept or host user-provided content or advertisements which could contain specially crafted content that could exploit this vulnerability.

The script could take any action on the user's behalf that the Web site is authorized to take. This could include monitoring the Web session and forwarding information to a third party, running other code on the user's system, and reading or writing cookies.

What causes the vulnerability?
A cross-site scripting (XSS) vulnerability results from the way that .NET Framework 2.0 validates the value of an HTTP request.

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. This enables developers to build Web-based applications with the same richness and functionality usually associated with applications built in languages such as Visual Basic or Visual C++. Because ASP.NET is a Web-based application environment, it requires an underlying Web server to provide basic HTTP functionality. For this reason, 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 is AutoPostBack?
AutoPostBack is a property supported by controls in a form. Forms using a control that supports this property can set the value of this property to true (the default value is false) which results in control posting back to the server each time a user interacts with the control.

What is cross-site scripting?
Cross-site scripting (XSS) is a class of security vulnerability that can enable an attacker to "inject" script code into a user's session with a Website. The vulnerability can affect Web servers that dynamically generate HTML pages. If these servers embed browser input in the dynamic pages that they send back to the browser, these servers can be manipulated to include maliciously supplied content in the dynamic pages. This can allow malicious script to be executed. Web browsers may perpetuate this problem through their assumptions of "trusted" sites and their use of cookies to maintain persistent state with the Websites that they frequent. An XSS attack does not modify Website content. Instead, it inserts new, malicious script that can execute at the browser in the context that is associated with a trusted server.

How does cross-site scripting work?
Web pages contain text and HTML markup. Text and HTML markup are generated by the server and are interpreted by the client. If untrusted content is introduced into a dynamic page, neither the server nor the client has sufficient information to recognize that this injection has occurred and to take protective measures.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability on a server running a vulnerable version of the .Net Framework 2.0, could inject a client side script in the user's browser. The script could spoof content, disclose information, or take any action that the user could take on the affected web site. Attempts to exploit this vulnerability would require user interaction.

Who could exploit the vulnerability?
In an e-mail attack scenario an attacker could exploit the vulnerability by sending a specially crafted e-mail message to a user of a server that is running an affected software application. The attacker could then persuade the user to click a link in the e-mail message.

In a Web-based attack scenario a compromised Web an attacker could inject a client side script in the user's browser. The script could spoof content, disclose information, or take any action that the user could take on the affected web site. Attempts to exploit this vulnerability would require user interaction.

What systems are primarily at risk from the vulnerability?
Internet facing systems are primarily at risk from this vulnerability. In addition, internal Web sites that use ASP.NET to host sensitive data can be at risk from this vulnerability.

Could the vulnerability be exploited over the Internet?
Yes. An attacker could try to exploit this vulnerability over the Internet.

What does the update do?
The update removes the vulnerability by modifying the way that .ASP.NET validates the value of a HTTP request.

When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.

Affected Software:

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

Microsoft .NET Framework version 2.0

Prerequisites
This security update requires Microsoft .NET Framework version 2.0.

Microsoft Windows Installer 3.1 must be installed. To install the latest version of Windows Installer, visit the following Microsoft Web site:

Windows Installer 3.1 Redistributable (v2)

Inclusion in Future Service Packs:
The update for this issue will be included in a future service pack.

Installation Information

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/help Displays the command-line options.
Setup Modes
/q[n|b|r|f] Sets user interface level.
n - No user interaction
b - Basic user interaction
r - Reduced user interaction
f - Full user interaction (default)
Install Options
/extract [directory] Extract the package to the specified directory.
Restart Options
/norestart Does not restart when installation has completed.
/forcerestart Restarts the computer after installation and forces other applications to close at shutdown without saving open files first.
/promptrestart Display a dialog box prompting the local user to allow a restart.
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>

Note You can combine these switches into one command. For more information about the supported installation switches, see Microsoft Knowledge Base Article 824687. For more information about the Windows Installer, visit the Windows Installer MSDN web site.

Deployment Information

To install the security update without any user intervention, use the following use the applicable command at a command prompt:

NDP20-KB922770-x86.exe /qn

NDP20-KB922770-x64.exe /qn

NDP20-KB922770-ia64.exe /qn

Note Use of the /qn switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /qn switch.

To install the security update without forcing the system to restart, use the following applicable command at a command prompt:

NDP20-KB922770-x86.exe /norestart

NDP20-KB922770-x64.exe /norestart

NDP20-KB922770-ia64.exe /norestart

For information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site.

Restart Requirement
This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.

To help reduce the chance that a reboot will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart your computer, see Microsoft Knowledge Base Article 887012.

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

File Information
The English version of this update has the file attributes (or later) 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 version 2.0

File NameVersionDateTimeSize
aspnet_wp.exe2.0.50727.21013-Sep-200600:1023,040
webengine.dll2.0.50727.21013-Sep-200600:10300,032
System.web.dll2.0.50727.21013-Sep-200600:115,029,888

Microsoft .NET Framework version 2.0 on Windows Server, 2003 Enterprise Edition for Itanium-based Systems; Windows Server 2003, Datacenter Edition for Itanium-based Systems; Windows Server 2003, Enterprise Edition with SP1 for Itanium-based Systems; and Windows Server 2003, Datacenter Edition with SP1 for Itanium-based Systems:

File NameVersionDateTimeSize
aspnet_wp.exe2.0.50727.21012-Sep-200604:1873,728
aspnet_wp.exe2.0.50727.21013-Sep-200600:1023,040
webengine.dll2.0.50727.21012-Sep-200604:18868,864
webengine.dll2.0.50727.21013-Sep-200600:10300,032
System.web.dll2.0.50727.21012-Sep-200608:244,599,808
System.web.dll2.0.50727.21013-Sep-200600:115,029,888

Microsoft .NET Framework version 2.0 for Windows Server 2003, Standard x64 Edition; Windows Server 2003, Enterprise x64 Edition; and Windows Server 2003, Datacenter x64 Edition; Windows Server 2003 R2, Standard x64 Edition; Windows Server 2003 R2, Enterprise x64 Edition; and Windows Server 2003 R2, Datacenter x64 Edition:

File NameVersionDateTimeSize
aspnet_wp.exe2.0.50727.21012-Sep-200604:1134,816
aspnet_wp.exe2.0.50727.21013-Sep-200600:1023,040
webengine.dll2.0.50727.21012-Sep-200604:11540,672
webengine.dll2.0.50727.21013-Sep-200600:10300,032
System.web.dll2.0.50727.21012-Sep-200607:324,964,352
System.web.dll2.0.50727.21013-Sep-200600:115,029,888

Verifying Update Installation

File Version Information

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

Obtaining Other Security Updates:

Updates for other security issues are available at the following locations:

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.

Security Resources:

Software Update Services:

By using Microsoft Software Update Services (SUS), administrators can quickly and reliably deploy the latest critical updates and security updates to Windows 2000 and Windows Server 2003-based servers, and to desktop systems that are running Windows 2000 Professional or Windows XP Professional.

For more information about how to deploy security updates by using Software Update Services, visit the Software Update Services Web site.

Windows Server Update Services:

By using Windows Server Update Services (WSUS), administrators can quickly and reliably 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 onto Windows 2000 and later operating systems.

For more information about how to deploy security updates using Windows Server Update Services, visit the Windows Server Update Services Web site.

Systems Management Server:

Microsoft Systems Management Server (SMS) delivers a highly configurable enterprise solution for managing updates. By using SMS, administrators can identify Windows-based systems that require security updates and can perform controlled deployment of these updates throughout the enterprise with minimal disruption to end users. For more information about how administrators can use SMS 2003 to deploy security updates, visit the SMS 2003 Security Patch Management Web site. SMS 2.0 users can also use Software Updates Service Feature Pack to help deploy security updates. For information about SMS, visit the SMS Web site.

Note SMS uses the Microsoft Baseline Security Analyzer, the Microsoft Office Detection Tool, and the Enterprise Update Scan Tool to provide broad support for security bulletin update detection and deployment. Some software updates may not be detected by these tools. Administrators can use the inventory capabilities of the SMS in these cases to target updates to specific systems. For more information about this procedure, visit the following Web site. Some security updates require administrative rights following a restart of the system. Administrators can use the Elevated Rights Deployment Tool (available in the SMS 2003 Administration Feature Pack and in the SMS 2.0 Administration Feature Pack) to install these updates.

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 (October 10, 2006): Bulletin published.
  • V1.1 (October 11, 2006): Bulletin updated “Caveats” Section and “What are the known issues that customers may experience when they install this security update?” under the “Frequently Asked Questions (FAQ) Related to This Security Update” section.
  • V1.2 (October 25, 2006): Bulletin updated “Non-Affected Software” for Microsoft Windows Server 2003 for Itanium-based Systems. “Why is Microsoft Windows Server 2003 for Itanium-based Systems listed in the “Non-Affected Software” section?” and “Why does Microsoft .NET Framework 2.0 does not install on Microsoft Windows Server 2003 for Itanium-based systems?” under the “Frequently Asked Questions (FAQ) Related to This Security Update” section.
  • V1.3 (November 29, 2006): Bulletin updated “Caveats” Section and “What are the known issues that customers may experience when they install this security update?” under the “Frequently Asked Questions (FAQ) Related to This Security Update” section.

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

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.