Computer Security
[EN] securityvulns.ru no-pyccku


Related information

  Microsoft Windows multiple security vulnerabilities

  [CORE-2010-0624] MS OpenType CFF Parsing Vulnerability

  Microsoft Security Bulletin MS10-085 - Important Vulnerability in SChannel Could Allow Denial of Service (2207566)

  Microsoft Security Bulletin MS10-081 - Important Vulnerability in Windows Common Control Library Could Allow Remote Code Execution (2296011)

  Microsoft Security Bulletin MS10-078 - Important Vulnerabilities in the OpenType Font (OTF) Format Driver Could Allow Elevation of Privilege (2279986)

From:MICROSOFT <secure_(at)_microsoft.com>
Date:13.10.2010
Subject:Microsoft Security Bulletin MS10-084 - Important Vulnerability in Windows Local Procedure Call Could Cause Elevation of Privilege (2360937)

Microsoft Security Bulletin MS10-084 - Important
Vulnerability in Windows Local Procedure Call Could Cause Elevation of Privilege (2360937)
Published: October 12, 2010

Version: 1.0
General Information
Executive Summary

This security update resolves a publicly disclosed vulnerability in Microsoft Windows. This security update is rated Important for all supported editions of Windows XP and Windows Server 2003. All supported editions of Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 are not affected by the vulnerability. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The vulnerability could allow elevation of privilege if an attacker logs on to an affected system and runs specially crafted code that sends an LPC message to the local LRPC Server. The message could then allow an authenticated user to access resources that are running in the context of the NetworkService account. An attacker must have valid logon credentials and be able to log on locally to exploit this vulnerability.

The security update addresses the vulnerability by modifying the way LRPC port messages are handled within the RPC subsystem. For more information about the vulnerability, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.

Recommendation. The majority of customers have automatic updating enabled and will not need to take any action because this security update will be downloaded and installed automatically. Customers who have not enabled automatic updating need to check for updates and install this update manually. For information about specific configuration options in automatic updating, see Microsoft Knowledge Base Article 294871.

For administrators and enterprise installations, or end users who want to install this security update manually, Microsoft recommends that customers apply the update at the earliest opportunity using update management software, or by checking for updates using the Microsoft Update service.

See also the section, Detection and Deployment Tools and Guidance, later in this bulletin.

Known Issues. None
Top of sectionTop of section
Affected and Non-Affected Software

The following software have been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle.

Affected Software
Operating System Maximum Security Impact Aggregate Severity Rating Bulletins Replaced by this Update

Windows XP Service Pack 3


Elevation of Privilege


Important


MS10-066

Windows XP Professional x64 Edition Service Pack 2


Elevation of Privilege


Important


MS10-066

Windows Server 2003 Service Pack 2


Elevation of Privilege


Important


MS10-066

Windows Server 2003 x64 Edition Service Pack 2


Elevation of Privilege


Important


MS10-066

Windows Server 2003 with SP2 for Itanium-based Systems


Elevation of Privilege


Important


MS10-066

Non-Affected Software
Operating System

Windows Vista Service Pack 1 and Windows Vista Service Pack 2

Windows Vista x64 Edition Service Pack 1 and Windows Vista x64 Edition Service Pack 2

Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2

Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2

Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2

Windows 7 for 32-bit Systems

Windows 7 for x64-based Systems

Windows Server 2008 R2 for x64-based Systems

Windows Server 2008 R2 for Itanium-based Systems
Top of sectionTop of section

Frequently Asked Questions (FAQ) Related to This Security Update

Where are the file information details?
Refer to the reference tables in the Security Update Deployment section for the location of the file information details.

I am using an older release of the software discussed in this security bulletin. What should I do?
The affected software listed in this bulletin have been tested to determine which releases are affected. Other releases are past their support life cycle. For more information about the product lifecycle, visit the Microsoft Support Lifecycle Web site.

It should be a priority for customers who have older releases of the software to migrate to supported releases to prevent potential exposure to vulnerabilities. To determine the support lifecycle for your software release, see Select a Product for Lifecycle Information. For more information about service packs for these software releases, see Lifecycle Supported Service Packs.

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 in the Contact Information list, 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 Microsoft Support Lifecycle Policy FAQ.
Top of sectionTop of section
Vulnerability Information

Severity Ratings and Vulnerability Identifiers

The following severity ratings assume the potential maximum impact of the vulnerability. For information regarding the likelihood, within 30 days of this security bulletin's release, of the exploitability of the vulnerability in relation to its severity rating and security impact, please see the Exploitability Index in the October bulletin summary. For more information, see Microsoft Exploitability Index.
Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected Software LPC Message Buffer Overrun Vulnerability - CVE-2010-3222 Aggregate Severity Rating

Windows XP Service Pack 3


Important
Elevation of Privilege


Important

Windows XP Professional x64 Edition Service Pack 2


Important
Elevation of Privilege


Important

Windows Server 2003 Service Pack 2


Important
Elevation of Privilege


Important

Windows Server 2003 x64 Edition Service Pack 2


Important
Elevation of Privilege


Important

Windows Server 2003 with SP2 for Itanium-based Systems


Important
Elevation of Privilege


Important
Top of sectionTop of section

LPC Message Buffer Overrun Vulnerability - CVE-2010-3222

An elevation of privilege vulnerability exists in the Remote Procedure Call Subsystem (RPCSS) running in the context of the NetworkService account, where a local application can use LPC to request that the LPC server connect back to the client using LRPC. This request could contain specially crafted data designed to cause a stack-based buffer overflow, allowing an authenticated user to access resources running in the context of the NetworkService account.

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

Mitigating Factors for LPC Message Buffer Overrun Vulnerability - CVE-2010-3222

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:


An attacker must have valid logon credentials and be able to log on locally to exploit this vulnerability.
Top of sectionTop of section

Workarounds for LPC Message Buffer Overrun Vulnerability - CVE-2010-3222

Microsoft has not identified any workarounds for this vulnerability.
Top of sectionTop of section

FAQ for LPC Message Buffer Overrun Vulnerability - CVE-2010-3222

What is the scope of the vulnerability?
This is an elevation of privilege vulnerability. An attacker with user credentials who successfully exploited this vulnerability could execute code in the context of the NetworkService account.

What causes the vulnerability?
This vulnerability is caused by a stack-based buffer overflow in the exchange of port messages between LPC and the LRPC Server (RPC EndPoint Mapper) contained within RPCSS.

What is the component affected by the vulnerability?
The component affected by the vulnerability is Microsoft Local Procedure Call (LPC), a component of Remote Procedure Call (RPC).

What is LPC?
Local Procedure Call (LPC) is a message-passing service included in Windows. This service allows threads and processes to communicate with each other. When a client process must request a service from a server process, there must be a way for the two processes to communicate with each other. There must be a way for the client process to make requests of the server, for the server to send responses to the client, and for each to determine their status. When the client process and the server process are located on different systems, Remote Procedure Call (RPC) is used. When they are located on the same system, LPC can be used.

What is RPC?
Remote Procedure Call (RPC) is an inter-process communication (IPC) mechanism that enables data exchange and invocation of functionality residing in a different process. That process can be on the same computer, on the local area network (LAN), or across the Internet. The Microsoft RPC mechanism uses other IPC mechanisms, such as named pipes, NetBIOS, or Winsock, to establish communications between the client and the server. With RPC, essential program logic and related procedure code can exist on different computers, which is important for distributed applications. For more information, see the TechNet article, What Is RPC?

What is LRPC?
Local RPC (LRPC) denotes RPC communication that takes place on a local system.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could run specially crafted code in the context of the NetworkService account, allowing it to gain access to resources that are running as NetworkService. Some of these processes may have the ability to elevate their privileges to LocalSystem, allowing any NetworkService processes to elevate their privileges to LocalSystem as well. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

How could an attacker exploit the vulnerability?
An attacker who has logged on locally with valid credentials could exploit the vulnerability by running specially crafted code that sends an LPC message to the local LRPC server. The message could then allow an authenticated user to execute code in the context of the NetworkService account.

What systems are primarily at risk from the vulnerability?
Workstations and terminal servers are primarily at risk. Servers could be at more risk if users who do not have sufficient administrative permissions are given the ability to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do?
The update addresses the vulnerability by modifying the way that LPC port messages are handled within RPCSS.

When this security bulletin was issued, had this vulnerability been publicly disclosed?
Yes. This vulnerability has been publicly disclosed. It has been assigned Common Vulnerability and Exposure number CVE-2010-3222.

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.

Other Information
Microsoft Active Protections Program (MAPP)

To improve security protections for customers, Microsoft provides vulnerability information to major security software providers in advance of each monthly security update release. Security software providers can then use this vulnerability information to provide updated protections to customers via their security software or devices, such as antivirus, network-based intrusion detection systems, or host-based intrusion prevention systems. To determine whether active protections are available from security software providers, please visit the active protections Web sites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners.

Support


Customers in the U.S. and Canada can receive technical support from Security Support or 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates. For more information about available support options, see Microsoft Help and Support.


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 (October 12, 2010): Bulletin published.

About | Terms of use | Privacy Policy
© SecurityVulns, 3APA3A, Vladimir Dubrovin
Nizhny Novgorod