Computer Security
[EN] securityvulns.ru no-pyccku


Related information

  Microsoft Windows Universal PnP memory corruption

  iDefense Security Advisory 04.10.07: Microsoft Windows Universal Plug and Play Memory Corruption Vulnerability

From:MICROSOFT <secure_(at)_microsoft.com>
Date:10.04.2007
Subject:Microsoft Security Bulletin MS07-019 Vulnerability in Universal Plug and Play Could Allow Remote Code Execution (931261)

Microsoft Security Bulletin MS07-019
Vulnerability in Universal Plug and Play Could Allow Remote Code Execution (931261)
Published: April 10, 2007

Version: 1.0
Summary

Who Should Read this Document: Customers who use Microsoft Windows

Impact of Vulnerability: Remote Code Execution

Maximum Severity Rating: Critical

Recommendation: Customers should apply the update immediately

Security Update Replacement: None

Caveats: None

Tested Software and Security Update Download Locations:

Affected Software:


Microsoft Windows XP Service Pack 2 — Download the update


Microsoft Windows XP Professional x64 Edition and Microsoft Windows XP Professional x64 Edition Service Pack 2— Download the update

Non-Affected Software:


Microsoft Windows 2000 Service Pack 4


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


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


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


Windows Vista


Windows Vista x64 Edition

The software in this list has been tested to determine whether the versions are affected. Other versions are either past their support life cycle or are not affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.
Top of sectionTop of section
General Information

Executive Summary

Executive Summary:

This update resolves a newly discovered, privately reported vulnerability. The vulnerability is documented in its own subsection in the Vulnerability Details section of this bulletin.

We recommend that customers apply the update immediately.

Severity Ratings and Vulnerability Identifiers:
Vulnerability Identifiers Impact of Vulnerability Microsoft Windows XP Service Pack 2

UPnP Memory Corruption Vulnerability - CVE-2007-1204


Remote Code Execution


Critical

This assessment is based on the types of systems that are affected by the vulnerability, their typical deployment patterns, and the effect that exploiting the vulnerability would have on them.

Note The severity ratings for non-x86 operating system versions map to the x86 operating system versions as follows:


The Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 severity ratings are the same as the Windows XP Service Pack 2 severity rating.
Top of sectionTop of section

Frequently Asked Questions (FAQ) Related to This Security Update

Can I use the Microsoft Baseline Security Analyzer (MBSA) to determine whether this update is required?
The following table provides the MBSA detection summary for this security update.
Product MBSA 1.2.1 MBSA 2.0.1

Microsoft Windows XP Service Pack 2


Yes


Yes

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


No


Yes

For more information about MBSA, visit the MBSA Web site. For more information about the programs that Microsoft Update and MBSA 2.0 currently do not detect, see Microsoft Knowledge Base Article 895660.

For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles.

Can I use Systems Management Server (SMS) to determine whether this update is required?
The following table provides the SMS detection summary for this security update.
Product SMS 2.0 SMS 2003

Microsoft Windows XP Service Pack 2


Yes


Yes

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


No


Yes

SMS 2.0 and SMS 2003 Software Update Services (SUS) Feature Pack can use MBSA 1.2.1 for detection and therefore have the same limitation that is listed earlier in this bulletin related to programs that MBSA 1.2.1 does not detect.

For SMS 2.0, the SMS SUS Feature Pack, which includes the Security Update Inventory Tool (SUIT), can be used by SMS to detect security updates. SMS SUIT uses the MBSA 1.2.1 engine for detection. For more information about SUIT, visit the following Microsoft Web site. For more information about the limitations of SUIT, see Microsoft Knowledge Base Article 306460. The SMS SUS Feature Pack also includes the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.

For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, visit the following Microsoft Web site. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.

For more information about SMS, visit the SMS Web site.

For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles.

I am using an older version of the software discussed in this security bulletin; what should I do?
The affected software listed in this bulletin has been tested to determine whether the versions are affected. Other versions are past their support life cycle. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.

It should be a priority for customers who have older versions of the software to migrate to supported versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the following Microsoft Support Lifecycle Web site. For more information about the extended security update support period for these operating system versions, visit the Microsoft Product Support Services Web site.

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, 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 Details

UPnP Memory Corruption Vulnerability - CVE-2007-1204:

A remote code execution vulnerability exists in the Universal Plug and Play service in the way that it handles specially crafted HTTP requests. An attacker who has successfully exploited this vulnerability could run arbitrary code in the context of local service.

Mitigating Factors for UPnP Memory Corruption Vulnerability - CVE-2007-1204:


An attacker who successfully exploited this vulnerability could run code in the context of the Local Service account only and could not run code under the Local SYSTEM account.


By default the UPnP service is set to manual on affected systems.


Firewall best practices and standard default firewall configurations can help protect networks from attacks that originate outside the enterprise perimeter. Best practices recommend that systems that are connected to the Internet have a minimal number of ports exposed.
Top of sectionTop of section

Workarounds for UPnP Memory Corruption Vulnerability - CVE-2007-1204:

Microsoft has tested the following workarounds. Although these workarounds will not correct the underlying vulnerability, they help block known attack vectors. When a workaround reduces functionality, it is identified in the following section.


Block the following at the firewall:


UDP port 1900 and TCP port 2869

The UPnP framework uses UDP port 1900 and TCP port 2869. Simple Service Discovery Protocol (SSDP) uses multicast searches to discover UPnP devices. Multicast searches are sent to UDP port 1900 using dynamic outgoing ports. Windows Firewall accepts matching multicast search replies that are received within three seconds of a multicast search. Afterward, the firewall will block multicast search replies, even if they match the search requests. For additional information on effects on the UPnP service when configuring the firewall, see Microsoft Knowledge Base Article 886257.

Impact of workaround:


The UPnP framework cannot discover networked UPnP devices that announce themselves. The firewall blocks these incoming announcements.


A control point running on another computer cannot find or control UPnP devices running on a computer running Windows XP SP2. The firewall blocks the incoming UPnP device-related messages.

How to undo workaround:

To undo the workaround, re-enable UDP port 1900 and TCP port 2869 on the firewall.


Disable the Universal Plug and Play service

Disabling the UPnP service will help protect the affected computer from attempts to exploit this vulnerability. To disable the UPnP service, follow these steps:

1.


Click Start and then click Control Panel. Alternatively, point to Settings and then click Control Panel.

2.


Double-click Administrative Tools.

3.


Double-click Services.

4.


Double-click Universal Plug and Play Device Host.

5.


In the Startup type list, click Disabled.

6.


Click Stop, and then click OK.

You can also stop and disable the UPnP service by using the following command at the command prompt:

sc stop UPnPHost &sc config UPnPHost start= disabled

Impact of workaround: If you disable the UPnP service, components that are dependent on the UPnP service may not operate correctly.

How to undo workaround:

To undo the workaround, re-enable the UPnP service. To do so, follow these steps:

1.


Click Start and then click Control Panel. Alternatively, point to Settings and then click Control Panel.

2.


Double-click Administrative Tools.

3.


Double-click Services.

4.


Double-click Universal Plug and Play Device Host.

5.


In the Startup type list, click Manual.

6.


Click Start, and then click OK.


To help protect from network-based attempts to exploit this vulnerability, enable advanced TCP/IP filtering on systems that support this feature.

You can enable advanced TCP/IP filtering to block all unsolicited inbound traffic. For more information about how to configure TCP/IP filtering, see Microsoft Knowledge Base Article 309798.


To help protect from network-based attempts to exploit this vulnerability, block the affected ports by using IPSec on the affected systems.

Use Internet Protocol security (IPSec) to help protect network communications. Detailed information about IPSec and about how to apply filters is available in Microsoft Knowledge Base Article 313190 and Microsoft Knowledge Base Article 813878.
Top of sectionTop of section

FAQ for UPnP Memory Corruption Vulnerability - CVE-2007-1204:

What is the scope of the vulnerability?
A remote code execution vulnerability exists in the Universal Plug and Play (UPnP) service in the way that it handles specially crafted HTTP requests. These HTTP requests could only be sent directly to a target computer by an attacker on the same subnet. The Windows XP firewall and the protocol enforce this subnet restriction. An attacker who successfully exploited this vulnerability could run arbitrary code in the context of the Local Service account.

What causes the vulnerability?
When the UPnP service handles specifically crafted HTTP requests it may corrupt system memory in such a way that an attacker could execute arbitrary code.

What is UPnP?
UPnP is a set of computer network protocols that extends Plug and Play to simplify the networking of intelligent devices in homes and businesses. When devices incorporating UPnP technology are physically connected to the network, they will connect automatically to one another over the network, without the need for user configuration or centralized servers.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take complete control of the affected system.

What systems are primarily at risk from the vulnerability?
Workstations and client computers are primarily at risk. Servers and terminal servers are not at risk as they do not include the affected UPnP component. Systems that have components installed that utilize UPnP functionality, may enable the UPnP service placing the system at risk.

Could the vulnerability be exploited over the Internet?
An attacker on the same subnet as the target computer could exploit this vulnerability. These HTTP requests could only be sent directly to a target computer by an attacker on the same subnet. In addition perimeter firewall best practices and standard perimeter firewall configurations can help protect against attacks that originate from the Internet.

What does the update do?
The update removes the vulnerability by modifying the way that UPnP validates HTTP requests before passing data to the allocated buffer.

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.

Acknowledgments

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


Greg MacManus of iDefense Labs for reporting the UPnP Memory Corruption Vulnerability (CVE-2007-1204).


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 (April 10, 2007): Bulletin published.

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