Computer Security
[EN] securityvulns.ru no-pyccku


Related information

  Microsoft Windows Tracing Feature for Services security vulnerabilities

From:MICROSOFT <secure_(at)_microsoft.com>
Date:11.08.2010
Subject:Microsoft Security Bulletin MS10-059 - Important Vulnerabilities in the Tracing Feature for Services Could Allow Elevation of Privilege (982799)

Microsoft Security Bulletin MS10-059 - Important
Vulnerabilities in the Tracing Feature for Services Could Allow Elevation of Privilege (982799)
Published: August 10, 2010

Version: 1.0
General Information
Executive Summary

This security update resolves one publicly disclosed vulnerability and one privately reported vulnerability in the Tracing Feature for Services. The vulnerabilities could allow elevation of privilege if an attacker runs a specially crafted application. An attacker must have valid logon credentials and be able to log on locally to exploit this vulnerability. The vulnerability could not be exploited remotely or by anonymous users.

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

The security update addresses the vulnerabilities by correcting the manner in which tokens are obtained and the length of a string read from the registry is calculated. 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. 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 Vista Service Pack 1 and Windows Vista Service Pack 2


Elevation of Privilege


Important


None

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 7 for 32-bit Systems


Elevation of Privilege


Important


None

Windows 7 for x64-based Systems


Elevation of Privilege


Important


None

Windows Server 2008 R2 for x64-based Systems*


Elevation of Privilege


Important


None

Windows Server 2008 R2 for Itanium-based Systems


Elevation of Privilege


Important


None

*Server Core installation affected. This update applies, with the same severity rating, to supported editions of Windows Server 2008 or Windows Server 2008 R2 as indicated, whether or not installed using the Server Core installation option. For more information on this installation option, see the TechNet articles, Managing a Server Core Installation and Servicing a Server Core Installation. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008 and Windows Server 2008 R2; see Compare Server Core Installation Options.

Non-Affected Software
Operating System

Windows XP Service Pack 3

Windows XP Professional x64 Edition Service Pack 2

Windows Server 2003 Service Pack 2

Windows Server 2003 x64 Edition Service Pack 2

Windows Server 2003 with SP2 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.

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 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 August bulletin summary. For more information, see Microsoft Exploitability Index.
Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected Software Tracing Registry Key ACL Vulnerability - CVE-2010-2554 Tracing Memory Corruption Vulnerability - CVE-2010-2555 Aggregate Severity Rating

Windows Vista Service Pack 1 and Windows Vista Service Pack 2


Moderate
Elevation of Privilege


Important
Elevation of Privilege


Important

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


Moderate
Elevation of Privilege


Important
Elevation of Privilege


Important

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


Moderate
Elevation of Privilege


Important
Elevation of Privilege


Important

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


Moderate
Elevation of Privilege


Important
Elevation of Privilege


Important

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


Moderate
Elevation of Privilege


Important
Elevation of Privilege


Important

Windows 7 for 32-bit Systems


Moderate
Elevation of Privilege


Important
Elevation of Privilege


Important

Windows 7 for x64-based Systems


Moderate
Elevation of Privilege


Important
Elevation of Privilege


Important

Windows Server 2008 R2 for x64-based Systems*


Moderate
Elevation of Privilege


Important
Elevation of Privilege


Important

Windows Server 2008 R2 for Itanium-based Systems


Moderate
Elevation of Privilege


Important
Elevation of Privilege


Important

*Server Core installation affected. This update applies, with the same severity rating, to supported editions of Windows Server 2008 or Windows Server 2008 R2 as indicated, whether or not installed using the Server Core installation option. For more information on this installation option, see the TechNet articles, Managing a Server Core Installation and Servicing a Server Core Installation. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008 and Windows Server 2008 R2; see Compare Server Core Installation Options.
Top of sectionTop of section

Tracing Registry Key ACL Vulnerability - CVE-2010-2554

An elevation of privilege vulnerability exists when Windows places incorrect access control lists (ACLs) on the registry keys for the Tracing Feature for Services. The vulnerability could allow an attacker to run code with elevated privileges. 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-2010-2554.

Mitigating Factors for Tracing Registry Key ACL Vulnerability - CVE-2010-2554

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. The vulnerability could not be exploited remotely or by anonymous users.
Top of sectionTop of section

Workarounds for Tracing Registry Key ACL Vulnerability - CVE-2010-2554

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

FAQ for Tracing Registry Key ACL Vulnerability - CVE-2010-2554

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 Windows places incorrect access control lists (ACLs) on registry keys for the Tracing Feature for Services. This makes it possible for an attacker to modify the tracing directory to a named pipe and create a named pipe listener on it. Once the named pipe is created, the attacker can impersonate it to obtain the tokens of the service creating the named pipe. If the creator is running in Local System context (for example, IpHlpSvc service), then the attacker can obtain and use the tokens of the Local System.

What is an Access Control List (ACL)?
An access control list (ACL) is a list of security protections that applies to an object. An object can be a file, process, event, or any entity having a security descriptor. An entry in an ACL is an access control entry (ACE). There are two types of access control list: discretionary and system. Each ACE in an ACL identifies access rights allowed, denied, or audited for that trustee. For additional information, see the MSDN article, Access Control Lists.

What is a named pipe?
A named pipe is a named, one-way or duplex pipe for communication between the pipe server and one or more pipe clients. All instances of a named pipe share the same pipe name, but each instance has its own buffers and handles, and provides a separate conduit for client/server communication. The use of instances enables multiple pipe clients to use the same named pipe simultaneously. Any process can access named pipes, subject to security checks, making named pipes an easy form of communication between related or unrelated processes. For more information, see MSDN article, Named Pipes.

What is the Routing Utilities Component (rtutils.dll)?
The routing utilities component (rtutils.dll) is a module that contains functions used for tracing, providing a uniform mechanism for generating diagnostic output for the various service components. When a component uses the Rtutils tracing mechanism, component specific tracing settings stored at the registry under the HKLM\Software\Microsoft\Tracing\ key will be used for storing the tracing data.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could run arbitrary code with system-level privileges. 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?
To exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially crafted application that could exploit the vulnerability and take complete control over the affected system.

What systems are primarily at risk from the vulnerability?
Workstations and terminal servers are primarily at risk. Servers could be at more risk if administrators allow users 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 correcting the manner in which tokens are obtained via impersonation.

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

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 when this security bulletin was originally issued.
Top of sectionTop of section
Top of sectionTop of section

Tracing Memory Corruption Vulnerability - CVE-2010-2555

An elevation of privilege vulnerability exists due to the way that the Tracing Feature for Services allocates memory when processing specially crafted long strings from the registry. An attacker who successfully exploited this vulnerability could run arbitrary code with system-level privileges. 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-2010-2555.

Mitigating Factors for Tracing Memory Corruption Vulnerability - CVE-2010-2555

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. The vulnerability could not be exploited remotely or by anonymous users.
Top of sectionTop of section

Workarounds for Tracing Memory Corruption Vulnerability - CVE-2010-2555

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

FAQ for Tracing Memory Corruption Vulnerability - CVE-2010-2555

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 Tracing Feature for Services incorrectly calculates the length of certain strings read from the registry.

What is the Routing Utilities Component (rtutils.dll)?
The routing utilities component (rtutils.dll) is a module that contains functions used for tracing, providing a uniform mechanism for generating diagnostic output for the various service components. When a component uses the Rtutils tracing mechanism, component-specific tracing settings stored in the registry under the HKLM\Software\Microsoft\Tracing\ key will be used for storing the tracing data.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could run arbitrary code with system-level privileges. 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?
To exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially crafted application that could exploit the vulnerability and take complete control over the affected system.

What systems are primarily at risk from the vulnerability?
Workstations and terminal servers are primarily at risk. Servers could be at more risk if administrators allow users 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 correcting the manner in which the Tracing Features for Services calculates the length of a string read from the registry.

When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through coordinated vulnerability disclosure.

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 when this security bulletin was originally issued.

Other Information
Acknowledgments

Microsoft thanks the following for working with us to help protect customers:


Cesar Cerrudo of Argeniss for working with us on the Tracing Registry Key ACL Vulnerability (CVE-2010-2554)


Cesar Cerrudo of Argeniss for working with us on the Tracing Memory Corruption Vulnerability (CVE-2010-2555)
Top of sectionTop of section
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 (August 10, 2010): Bulletin published.

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