[NT] Universal Plug and Play Remote Code Execution (MS07-019)
- From: SecuriTeam <support@xxxxxxxxxxxxxx>
- Date: 11 Apr 2007 17:08:40 +0200
The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com
- - promotion
The SecuriTeam alerts list - Free, Accurate, Independent.
Get your security news from a reliable source.
http://www.securiteam.com/mailinglist.html
- - - - - - - - -
Universal Plug and Play Remote Code Execution (MS07-019)
------------------------------------------------------------------------
SUMMARY
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.
DETAILS
Affected Software:
* Microsoft Windows XP Service Pack 2 -
<http://www.microsoft.com/downloads/details.aspx?FamilyId=ecf69778-91f9-498e-a8bd-35208aa93051> Download the update
* Microsoft Windows XP Professional x64 Edition and Microsoft Windows XP
Professional x64 Edition Service Pack 2 -
<http://www.microsoft.com/downloads/details.aspx?FamilyId=6ceb5b4f-861f-4f37-b4bc-e8a56382b833> 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
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.
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
<http://support.microsoft.com/kb/886257> 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
<http://support.microsoft.com/kb/309798> 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 <http://support.microsoft.com/kb/313190>
Microsoft Knowledge Base Article 313190 and
<http://support.microsoft.com/kb/813878> Microsoft Knowledge Base Article
813878.
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.
ADDITIONAL INFORMATION
The information has been provided by Microsoft Security Bulletin MS07-019.
The original article can be found at:
<http://www.microsoft.com/technet/security/bulletin/ms07-019.mspx>
http://www.microsoft.com/technet/security/bulletin/ms07-019.mspx
========================================
This bulletin is sent to members of the SecuriTeam mailing list.
To unsubscribe from the list, send mail with an empty subject line and body to: list-unsubscribe@xxxxxxxxxxxxxx
In order to subscribe to the mailing list, simply forward this email to: list-subscribe@xxxxxxxxxxxxxx
====================
====================
DISCLAIMER:
The information in this bulletin is provided "AS IS" without warranty of any kind.
In no event shall we be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages.
- Prev by Date: [NT] Kaspersky Internet Security Suite klif.sys Heap Overflow Vulnerability
- Next by Date: [NT] Microsoft Content Management Server Remote Code Execution (MS07-018)
- Previous by thread: [NT] Kaspersky Internet Security Suite klif.sys Heap Overflow Vulnerability
- Next by thread: [NT] Microsoft Content Management Server Remote Code Execution (MS07-018)
- Index(es):
Relevant Pages
|
