Computer Security
[EN] securityvulns.ru no-pyccku


Related information

  Microsoft Windows RPC privilege escalation

From:MICROSOFT <secure_(at)_microsoft.com>
Date:10.06.2009
Subject:Microsoft Security Bulletin MS09-026 - Important Vulnerability in RPC Could Allow Elevation of Privilege (970238)

Microsoft Security Bulletin MS09-026 - Important
Vulnerability in RPC Could Allow Elevation of Privilege (970238)
Published: June 9, 2009

Version: 1.0
General Information
Executive Summary

This security update resolves a publicly disclosed vulnerability in the Windows remote procedure call (RPC) facility where the RPC Marshalling Engine does not update its internal state appropriately. The vulnerability could allow an attacker to execute arbitrary code and take complete control of an affected system. Supported editions of Microsoft Windows are not delivered with any RPC servers or clients that are subject to exploitation of this vulnerability. In a default configuration, users could not be attacked by exploitation of this vulnerability. However, the vulnerability is present in the Microsoft Windows RPC runtime and could affect third-party RPC applications.

This security update is rated Important for all supported editions of Microsoft Windows 2000, Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The update addresses the vulnerability by correcting the way that the RPC Marshalling Engine updates its internal state. 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

Microsoft Windows 2000 Service Pack 4


Elevation of Privilege


Important


MS07-058

Windows XP Service Pack 2


Elevation of Privilege


Important


MS07-058

Windows XP Service Pack 3


Elevation of Privilege


Important


None

Windows XP Professional x64 Edition Service Pack 2


Elevation of Privilege


Important


MS07-058

Windows Server 2003 Service Pack 2


Elevation of Privilege


Important


MS07-058

Windows Server 2003 x64 Edition Service Pack 2


Elevation of Privilege


Important


MS07-058

Windows Server 2003 with SP2 for Itanium-based Systems


Elevation of Privilege


Important


MS07-058

Windows Vista


Elevation of Privilege


Important


MS07-058

Windows Vista Service Pack 1 and Windows Vista Service Pack 2


Elevation of Privilege


Important


None

Windows Vista x64 Edition


Elevation of Privilege


Important


MS07-058

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


Elevation of Privilege


Important


None

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


Elevation of Privilege


Important


None

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


Elevation of Privilege


Important


None

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


Elevation of Privilege


Important


None

*Windows Server 2008 server core installation affected. For supported editions of Windows Server 2008, this update applies, with the same severity rating, whether or not Windows Server 2008 was installed using the Server Core installation option. For more information on this installation option, see Server Core. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008; see Compare Server Core Installation Options.
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. To determine the support life cycle for your software release, visit Microsoft Support Lifecycle.

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. For more information about the Windows Product Lifecycle, visit Microsoft Support Lifecycle. For more information about the extended security update support period for these software versions or editions, visit Microsoft Product Support Services.

Customers who require custom support for older releases 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 Microsoft Worldwide Information, 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.
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 June bulletin summary. For more information, see Microsoft Exploitability Index.
Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected Software RPC Marshalling Engine Vulnerability - CVE-2009-0568 Aggregate Severity Rating

Microsoft Windows 2000 Service Pack 4


Important
Elevation of Privilege


Important

Windows XP Service Pack 2 and 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

Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2


Important
Elevation of Privilege


Important

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


Important
Elevation of Privilege


Important

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


Important
Elevation of Privilege


Important

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


Important
Elevation of Privilege


Important

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


Important
Elevation of Privilege


Important

*Windows Server 2008 server core installation affected. For supported editions of Windows Server 2008, this update applies, with the same severity rating, whether or not Windows Server 2008 was installed using the Server Core installation option. For more information on this installation option, see Server Core. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008; see Compare Server Core Installation Options.
Top of sectionTop of section

RPC Marshalling Engine Vulnerability - CVE-2009-0568

An elevation of privilege vulnerability exists in the Windows remote procedure call (RPC) facility where the RPM Marshalling Engine does not update its internal state appropriately. The failure to update internal state could lead to a pointer being read from an incorrect location. An attacker who successfully exploited this vulnerability could execute arbitrary code and take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

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

Mitigating Factors for RPC Marshalling Engine Vulnerability - CVE-2009-0568

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:


Supported editions of Microsoft Windows are not delivered with any RPC servers or clients that are subject to exploitation of this vulnerability. In a default configuration, users could not be attacked by exploitation of this vulnerability. However, the vulnerability exists in the Microsoft Windows RPC runtime and could affect third-party RPC applications.
Top of sectionTop of section

Workarounds for RPC Marshalling Engine Vulnerability - CVE-2009-0568

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

FAQ for RPC Marshalling Engine Vulnerability - CVE-2009-0568

What is the scope of the vulnerability?
This is an elevation of privilege vulnerability. An attacker who successfully exploited this vulnerability could execute arbitrary code and take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

What causes the vulnerability?
The vulnerability is caused when the Remote Procedure Call (RPC) Marshalling Engine does not update its internal state in an appropriate manner. This failure to update could lead to a pointer being read from an incorrect location. Only interfaces using the Interface Definition Language (IDL) that contain a non-conformant varying array can be affected by this issue.

What RPC applications may be affected by this vulnerability?
To determine whether an application is affected by this issue, users must have access to the IDL file used to compile the client or server application. RPC applications may be vulnerable to exploitation of this vulnerability if the resulting stub contains a FC_SMVARRAY or FC_LGVARRAY followed by FC_VARIABLE REPEAT and FC_VARIABLE_OFFSET.

What is Remote Procedure Call (RPC)?
Microsoft Remote Procedure Call (RPC) is an interprocess 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 the RPC Marshalling Engine?
The RPC Marshalling Engine, also known as NDR, provides a common RPC interface between RPC clients and servers. NDR20 is used in a 32-bit architecture and NDR64 is optimized for a 64-bit architecture. The same marshalling engine is used on both the client and the server side, regardless of program architecture. The client and the server negotiate which marshalling engine is used for the communication.

What are Interface Definition Language (IDL)files and Application Configuration Files (ACF)?
The Interface Definition Language (IDL) file contains a description of the interface between the client and the server programs. RPC applications use the application configuration file (ACF) to describe the characteristics of the interface that are specific to the hardware and operating system that make up a particular operating environment. The purpose of dividing this information into two files is to keep the software interface separate from characteristics that affect only the operating environment.

The IDL file specifies a network contract for what is transmitted between the client and server. Keeping this information distinct from the information about the operating environment makes the IDL file portable to other environments. The IDL file consists of two parts: an interface header and an interface body.

The ACF specifies attributes that affect only local performance rather than the network contract. Microsoft RPC allows you to combine the ACF and IDL attributes in a single IDL file. You can also combine multiple interfaces in a single IDL file (and its ACF). For more information, see the MSDN article, The IDL and ACF Files.

What are Interprocess Communications (IPC)?
The Microsoft Windows operating system provides mechanisms for facilitating communications and data sharing between applications. Collectively, the activities enabled by these mechanisms are called interprocess communications (IPC). Some forms of IPC facilitate the division of labor among several specialized processes. Other forms of IPC facilitate the division of labor among computers on a network. For more information, see the MSDN article, Interprocess Communications.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could run arbitrary code with elevated permissions. 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 could exploit the vulnerability by creating a specially crafted RPC message and sending the message to an affected system over an affected TCP or UDP port. The message could then allow the client to write arbitrary data to memory in the RPC server address space. Only IDL interfaces containing a non-conformant varying array are affected by this issue.

What systems are primarily at risk from the vulnerability?
Both workstations and servers are at risk. Systems that allow RPC traffic from untrusted networks could be at more risk.

What does the update do?
The update addresses the vulnerability by correcting the way the RPC Marshalling Engine updates its internal state.

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-2009-0568.

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 (June 9, 2009): Bulletin published.

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