Secunia
Login
|
|
|
|
|
|
|
|
|
Microsoft Windows MSDTC and COM+ Vulnerabilities
Release Date: 2005-10-11 Last Update: 2005-11-21 Views: 29,124
Secunia Advisory SA17161
Where:
From local network
Impact:
Privilege escalation, DoS, System access,
Solution Status:
Vendor Patch
Operating System:
CVE Reference(s):
Description
Some vulnerabilities have been reported in Microsoft Windows, which can be exploited by malicious, local users to gain escalated privileges, or by malicious people to cause a DoS (Denial of Service) or compromise a vulnerable system.
1) A memory allocation error in the MSDTC (Microsoft Distributed Transaction Coordinator) interface proxy can be exploited to execute arbitrary code or to gain escalated privileges. The vulnerability is caused due to an error in the "MIDL_user_allocate()" function which allocates a single 4KB page of memory regardless of the actual amount of memory requested.
The vulnerability has been reported in the following versions:
* Windows 2000
* Windows XP Service Pack 1
* Windows Server 2003
2) An error in COM+ can be exploited to execute arbitrary code on a vulnerable system via a specially crafted network message, or to gain escalated privileges by running a specially crafted application.
The vulnerability has been reported in the following versions:
* Windows 2000 (remote code execution)
* Windows XP Service Pack 1 (remote code execution)
* Windows XP Service Pack 2 (local privilege escalation)
* Windows Server 2003 (local privilege escalation)
* Windows Server 2003 Service Pack 1 (local privilege escalation)
3) An error in the MSDTC when validating TIP (Transaction Internet Protocol) requests can lead to a DoS. This can be exploited by sending a sequence of commands to cause the MSDTC service to connect-back to a malicious server. The malicious server can then send an unexpected protocol command during the reconnection request to crash the MSDTC server.
Successful exploitation requires that the TIP protocol is enabled for MSDTC.
4) An error in the MSDTC when validating TIP (Transaction Internet Protocol) requests can be exploited to cause the MSDTC service to flood a specific IP address and port via a specific sequence of commands.
Successful exploitation requires that the TIP protocol is enabled for MSDTC.
Solution:
Apply patches.
Further details available to Secunia VIM customers
Provided and/or discovered by:
1) Fang Xing, eEye Digital Security
2) Cesar Cerrudo, Argeniss
3-4) Discovered by anonymous person and reported via iDEFENSE.
Original Advisory:
MS05-051 (KB902400):
http://www.microsoft.com/technet/security/Bulletin/MS05-051.mspx
eEye Digital Security:
http://www.eeye.com/html/research/advisories/AD20051011b.html
iDEFENSE:
http://www.idefense.com/application/poi/display?id=319
http://www.idefense.com/application/poi/display?id=320
Deep Links:
Links available to Secunia VIM customers
Do you have additional information related to this advisory?
Please provide information about patches, mitigating factors, new versions, exploits, faulty patches, links, and other relevant data by posting comments to this Advisory. You can also send this information to vuln@secunia.com
Subject: Microsoft Windows MSDTC and COM+ Vulnerabilities
|
No posts yet |
|
You must be logged in to post a comment. |
