Computer Security
[EN] securityvulns.ru no-pyccku


Related information

  Дырка в Microsoft Developer Studio (DCOM VB T-SQL debugger buffer overflow)

  Remote buffer overflow in DCOM VB T-SQL debugger

From:MICROSOFT <secure_(at)_microsoft.com>
Date:28.03.2001
Subject:Security Bulletin MS01-018

- ----------------------------------------------------------------------
Title:      Visual Studio VB-TSQL Object Contains Unchecked Buffer
Date:       27 March 2001
Software:   Visual Studio 6.0 Enterprise Edition
Impact:     Run code of attacker's choice
Bulletin:   MS01-018

Microsoft encourages customers to review the Security Bulletin at:
http://www.microsoft.com/technet/security/bulletin/MS01-018.asp.
- ----------------------------------------------------------------------

Issue:
======

The VB-TSQL debugger object that ships with Visual Studio 6.0
Enterprise Edition has an  unchecked buffer in the code that
processes parameters for one of the object's methods.  Theobject can,
by design, be programmatically accessed remotely. If the object were
to be  referenced by a program that contained specially malformed
data within the parameter,  eitherof two outcomes would result. In
the less serious case, the attacker could cause the  object to fail
on the hosting machine. In the more serious case, the attacker could
exploit  the buffer overrun to run code of the attacker's choice on
the hosting machine.

The debugger object (vbsdicli.exe) is installed by default with
Visual Studio 6.0 Enterprise  Edition and runs in the context of the
interactively logged-on user. The attacker could only  execute a
successful attack if he knew that a user had the component installed
and that the  user was logged in at the time of the attack.

Mitigating Factors:
===================

- If best practices have been followed and ports 137-139 and 445
have
  been blocked at an organization's router or firewall, this attack
  could not be executed from the Internet.

- There is no way to determine remotely if a machine has the
affected
  component installed. An attacker would need to successively target
  machines until he found one that was susceptible.

- The vulnerability could only be exploited if an interactive user
  were logged on to the target machine at the time of the malicious
  user's attack.

- Only the Enterprise Edition of Visual Studio 6.0 is affected.
  Visual Studio 6.0 Professional Edition is not affected.

Patch Availability:
===================

- A patch is available to fix this vulnerability. Please read the
  Security Bulletin
  http://www.microsoft.com/technet/security/bulletin/ms01-018.asp
  for information on obtaining this patch.

Acknowledgment:
===============

- BindView's Razor Team (http://razor.bindview.com)

- ---------------------------------------------------------------------

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.

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