Vulnerability: MS10-077 - Vulnerability in .NET Framework Could Allow Remote Code Execution (2160841)

  • Article ID: 112313
  • Updated: 04 Nov 2010

Back to Latest vulnerabilities homepage

Click any highlighted term for further explanation.

Details
Vulnerability name/brief description

MS10-077 - Vulnerability in .NET Framework Could Allow Remote Code Execution (2160841)

CVE/CAN name CVE-2010-3228
Vendor threat level Critical
SophosLabs threat level Medium
Solution

MS10-077

Vendor description This security update resolves a privately reported vulnerability in Microsoft .NET Framework. The vulnerability could allow remote code execution on a client system if a user views a specially crafted Web page using a Web browser that can run XAML Browser Applications (XBAPs). 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. The vulnerability could also allow remote code execution on a server system running IIS, if that server allows processing ASP.NET pages and an attacker succeeds in uploading a specially crafted ASP.NET page to that server and then executes the page, as could be the case in a Web hosting scenario.
This security update is rated Critical for Microsoft .NET Framework 4.0 on supported x64-based and Itanium-based editions of Microsoft Windows.
SophosLabs comments This remote code execution vulnerability takes place in either the context of the currently logged-on user, or in the context of the service account associated with an application pool identity.

This vulnerability exists due to the manner in which the .NET Framework JIT compiler optimizes code based on an incorrect assessment, which can lead to memory corruption and as a result, execution of arbitrary, unmanaged code.

There are 2 attack vectors for this vulnerability to be exploited, one is a Web browsing scenario and the other is a Web hosting scenario.

In the Web browsing scenario, an attacker could host a specially crafted Web site that contains a specially crafted XBAP (XAML browser application) that could exploit this vulnerability and then convince a user to view the Web site. The attacker could also take advantage of compromised Web sites and Web sites that accept or host user-provided content or advertisements.

In the Web hosting scenario, a Web hosting environment that allows users to upload custom ASP.NET applications could allow an attacker to upload a malicious ASP.NET application that uses this vulnerability to break out of the sandbox used to prevent ASP.NET code from performing harmful actions on the server system.

In both cases, once the exploit is successful, an attacker could either obtain the same permissions as the currently logged-on user or obtain the same permissions as the service account associated with the application pool identity of the application pool in which a Microsoft .NET application is running.

As this vulnerability is privately reported prior to the release of the patch, and coupled with the fact that SophosLabs have not seen any attempted exploits that leads us to assigning this vulnerability a threat level of Medium.

SophosLabs testing result N/A
Currently known exploits At the time of writing SophosLabs have not observed any malware attempting to exploit this vulnerability. Should this situation change samples will be analyzed and we will take action as necessary.
First sample seen N/A
Discovery date October 12, 2010
Affected software Microsoft .NET Framework 4.0 on Windows Server 2003 x64 Edition Service Pack 2
Microsoft .NET Framework 4.0 on Windows Server 2003 with SP2 for Itanium-based Systems
Microsoft .NET Framework 4.0 on Windows Vista x64 Edition Service Pack 1 and Windows Vista x64 Edition Service Pack 2
Microsoft .NET Framework 4.0 on Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2**
Microsoft .NET Framework 4.0 on Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2
Microsoft .NET Framework 4.0 on Windows 7 for x64-based Systems
Microsoft .NET Framework 4.0 on Windows Server 2008 R2 for x64-based Systems**
Microsoft .NET Framework 4.0 on Windows Server 2008 R2 for Itanium-based Systems

**Server Core installation not affected. The vulnerabilities addressed by this update do not affect supported editions of Windows Server 2008 or Windows Server 2008 R2 as indicated, when installed using the Server Core installation option.

References http://www.microsoft.com/technet/security/bulletin/MS10-077.mspx
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3228
Credits MAPP
Revisions October 12, 2010 - Initial analysis written

Explanation of terms

Vulnerability Name/Brief Description:
Vendor identifier plus a brief description of the type of attack.

CVE/CAN Name:
Currently assigned CVE name. If a CVE name doesn't exist the CAN name will be used until a CVE has been assigned.

Vendor Threat Level:

Threat level assigned by the vendor

SophosLabs Threat Level:
Threat level assigned by SophosLabs

  • LOW RISK - There is little chance of this vulnerability being actively exploited by malware.
  • MEDIUM RISK - There is a possibility of this vulnerability being actively exploited by malware.
  • HIGH RISK - There is a strong possibility of this vulnerability being actively exploited by malware.
  • CRITICAL RISK - This vulnerability will almost certainly be actively exploited by malware.

Solution:
Vendor-supplied Patch identifier and recommended solution, or workaround if applicable.

Vendor Description:
Summary of the cause and potential effect of the vulnerability provided by the vendor.

SophosLabs Comments:
SophosLabs' opinions and observations of the vulnerability in question.

SophosLabs Testing Result:
Details of completed lab testing, if applicable. Please note that the lab test environment may differ significantly from user environments.

Currently Known Exploits:
List of identities for known exploits, if applicable.

First Sample Seen:
Date of the first sample seen by SophosLabs.

Discovery Date:
Date of the earliest known publically disclosed advisory.

Affected Software:
Vulnerable platforms and software versions.

 
If you need more information or guidance, then please contact technical support.

Rate this article

Very poor Excellent

Comments