Microsoft Distributed Transaction Coordinator Two Vulnerabilities - Secunia Advisories - Vulnerability Information

Vulnerability Information

Vulnerability Scanning

Community

Blog

Corporate Information

Home > Vulnerability Information > Secunia Advisories > Microsoft Distributed Transaction Coordinator Two Vulnerabilities

Secunia Advisories

Advisories

Advisories by Product

Business Solutions Restricted

Partner Solutions Restricted

About

Microsoft Distributed Transaction Coordinator Two Vulnerabilities

Secunia Advisory:

SA20000

Advisory Toolbox:

Issue ticket

Save in to-do list

Mark as handled

Exploit information

Download as PDF

Review actions

Add comment

Release Date:

2006-05-09

Last Update:

2006-05-11

Popularity:

36,464 views

Critical:

Moderately critical

Impact:

DoS
System access

Where:

From local network

Solution Status:

Vendor Patch

OS:

Microsoft Windows 2000 Advanced Server
Microsoft Windows 2000 Datacenter Server
Microsoft Windows 2000 Professional
Microsoft Windows 2000 Server
Microsoft Windows NT 4.0 Server
Microsoft Windows NT 4.0 Server, Terminal Server Edition
Microsoft Windows Server 2003 Datacenter Edition
Microsoft Windows Server 2003 Enterprise Edition
Microsoft Windows Server 2003 Standard Edition
Microsoft Windows Server 2003 Web Edition
Microsoft Windows XP Home Edition
Microsoft Windows XP Professional

Secunia CVSS-2 Score:

Available in Secunia business solutions

Subscribe:

Instant alerts on relevant vulnerabilities

Advisory Content (Page 1 of 3)

[ 1 ] [ 2 ] [ 3 ]

Secunia is hiring, read about the open positions here!

Description:
Two vulnerabilities have been reported in Microsoft Windows, which can be exploited by malicious people to cause a DoS (Denial of Service) and potentially compromise a vulnerable system.

1) An out-of-bounds memory access error in the MSDTC (Microsoft Distributed Transaction Coordinator) can be exploited via a specially crafted BuildContextW request with a large UuidString or GuidIn string.

Successful exploitation causes the MSDTC component and dependent services to stop responding.

This vulnerability is related to vulnerability #1 in:
SA17161

2) A boundary error in the "CRpcIoManagerServer::BuildContext()" function in msdtcprx.dll within MSDTC can be exploited to cause a heap-based buffer overflow. According to the vendor, this causes the MSDTC component and dependent services to stop responding when receiving a specially crafted network message.

According to eEye Digital Security, this vulnerability can be exploited to execute arbitrary code on a vulnerable system.

Change Page:
[ 1 ] [ 2 ] [ 3 ]

Track this Secunia Advisory

Customers of the Secunia Vulnerability Intelligence solutions will automatically receive updates when new information regarding this advisory is released.

Read more about our Vulnerability Intelligence solutions and what they can do for you and your company.

About this Secunia Advisory

Please note: The information that this Secunia Advisory is based on comes from a third party unless stated otherwise.

Secunia collects, validates, and verifies all vulnerability reports issued by security research groups, vendors, and others.

Latest Advisories

10th Jul, 2009

New advisories:	11
New vulnerabilities:	18
Updated advisories:	46

Moderately // 84 views

Nwahy Products Security Bypass Vulnerability

Less // 109 views

ManageEngine NetFlow Analyzer 7 Cross-Site Scripting Vulnerabilities

Moderately // 97 views

Clear Content "url" Local File Inclusion Vulnerabilities

Moderately // 114 views

Universe CMS "id" SQL Injection Vulnerability

Highly // 95 views

OtsAV Products Ots File List Processing Buffer Overflow

Moderately // 167 views

Sun Solaris Tomcat Multiple Vulnerabilities

Moderately // 107 views

TalkBack Comment Edit Security Bypass

Moderately // 175 views

eEye Retina WiFi Scanner ".rws" Handling Buffer Overflow

Highly // 149 views

PatPlayer M3U Playlist Parsing Buffer Overflow

Less // 161 views

Red Hat update for httpd

Solutions | More...

Send Feedback to Secunia
If you have new information regarding this Secunia advisory or a product in our database, please send it to us using either our web form or email us at vuln@secunia.com. Ideas, suggestions, and other feedback are most welcome.