Computer Security
[EN] securityvulns.ru no-pyccku


Related information

  Microsoft Wndows Bluetooth stack code execution

From:MICROSOFT <secure_(at)_microsoft.com>
Date:11.06.2008
Subject:Microsoft Security Bulletin MS08-030 – Critical Vulnerability in Bluetooth Stack Could Allow Remote Code Execution (951376)

Microsoft Security Bulletin MS08-030 – Critical
Vulnerability in Bluetooth Stack Could Allow Remote Code Execution (951376)
Published: June 10, 2008

Version: 1.0
General Information
Executive Summary

This security update resolves a privately reported vulnerability in the Bluetooth stack in Windows that could allow remote code execution. An attacker who successfully exploited this vulnerability could 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.

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

The security update addresses the vulnerability by modifying the way that the Bluetooth stack handles a large number of service description requests. 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. Microsoft recommends that customers apply the update immediately.

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


Remote Code Execution


Critical


None

Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2


Remote Code Execution


Critical


None

Windows Vista and Windows Vista Service Pack 1


Remote Code Execution


Critical


None

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


Remote Code Execution


Critical


None

Non-Affected Software
Operating System

Microsoft Windows 2000 Service Pack 4

Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2

Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2

Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems

Windows Server 2008 for 32-bit Systems

Windows Server 2008 for x64-based Systems

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

Frequently Asked Questions (FAQ) Related to This Security Update

Where are the file information details?
The file information details can be found in Microsoft Knowledge Base Article 951376.

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
Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected Software Bluetooth Vulnerability - CVE-2008-1453 Aggregate Severity Rating

Windows XP Service Pack 2 and Windows XP Service Pack 3


Critical
Remote Code Execution


Critical

Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2


Critical
Remote Code Execution


Critical

Windows Vista and Windows Vista Service Pack 1


Critical
Remote Code Execution


Critical

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


Critical
Remote Code Execution


Critical
Top of sectionTop of section

Bluetooth Vulnerability - CVE-2008-1453

A remote code execution vulnerability exists in the Bluetooth stack in Microsoft Windows because the Bluetooth stack does not correctly handle a large number of service description requests. The vulnerability could allow an attacker to run code with elevated privileges. An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete date; 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-2008-1453.

Mitigating Factors for Bluetooth Vulnerability - CVE-2008-1453

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:


This vulnerability only affects systems with Bluetooth capability.
Top of sectionTop of section

Workarounds for Bluetooth Vulnerability - CVE-2008-1453

Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality.


Prevent the computer from accepting new Bluetooth connections

Interactive Method

1.


On the Control Panel, select Classic View.

2.


Select Bluetooth Devices.

3.


Click the Options tab.

4.


Clear the Allow Bluetooth devices to find this computer checkbox.

5.


Click OK.

How to undo the workaround

1.


On the Control Panel, select Classic View.

2.


Select Bluetooth Devices.

3.


Click the Options tab.

4.


Select the Allow Bluetooth devices to find this computer checkbox.

5.


Click OK.

PowerShell Script Method

Run the following commands as an elevated administrator:

$BthDriverKeys = Get-ChildItem "HKLM:\System\CurrentControlSet\Enum\usb" -recurse -ErrorAction SilentlyContinue | where {$_.GetValue("Service") -eq "BTHUSB"}
foreach($Key in $BthDriverKeys) { Set-ItemProperty -Path $Key.OpenSubKey("Device Parameters").Name.Replace("HKEY_LOCAL_MACHINE", "HKLM:") -Name "Write Scan Enable" -Value 0 }

How to undo the workaround

Run the following commands as an elevated administrator:

$BthDriverKeys = Get-ChildItem "HKLM:\System\CurrentControlSet\Enum\usb" -recurse -ErrorAction SilentlyContinue | where {$_.GetValue("Service") -eq "BTHUSB"}
foreach($Key in $BthDriverKeys) { Set-ItemProperty -Path $Key.OpenSubKey("Device Parameters").Name.Replace("HKEY_LOCAL_MACHINE", "HKLM:") -Name "Write Scan Enable" -Value 3 }


Turn off and disable the Bluetooth driver

You can stop and disable the driver by using the following command at the command prompt (available in Windows XP and above, and in the Windows 2000 Resource Kit):

sc config bthport start= disabled

How to undo the workaround

You can re-enable the Bluetooth driver by using the following command at the command prompt (available in Windows XP and above and in the Windows 2000 Resource Kit):

sc config bthport start= demand
Top of sectionTop of section

FAQ for Bluetooth Vulnerability - CVE-2008-1453

What is the scope of the vulnerability?
A remote code execution vulnerability exists in the Bluetooth stack in Microsoft Windows. An attacker who successfully exploited this vulnerability could run code with elevated privileges. An attacker could then take complete control of an affected system.

What causes the vulnerability?
The Windows Bluetooth Stack does not correctly handle a large number of service description requests.

What is Bluetooth?
Bluetooth is an industry-standard protocol that enables wireless connectivity for computers, handheld devices, mobile phones, and other devices. Visit the MSDN Bluetooth article for more information.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could gain complete control over the affected system. 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 have to rapidly send a large number of specially crafted Service Discovery Protocol (SDP) packets to an affected system. The way that the system reacts to those packets would allow the attacker to gain complete control over the affected system.

What systems are primarily at risk from the vulnerability?
All systems with Bluetooth enabled are at risk from this vulnerability.

What does the update do?
The update removes the vulnerability by improving the way that the Bluetooth stack handles a large number of SDP packets.

When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible 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 and had not seen any examples of proof of concept code published when this security bulletin was originally issued.

Other Information
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.

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 10, 2008): Bulletin published.

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