Computer Security
[EN] securityvulns.ru no-pyccku


Related information

  Multiple bugs in Microsoft SQL Server (multiple bugs)

  Microsoft SQL Server Webtasks privilege upgrade (#NISR17102002)

  Microsoft Security Bulletin MS02-061: Elevation of Privilege in SQL Server Web Tasks (Q316333)

  Security Bulletin MS02-056: Cumulative Patch for SQL Server (Q316333)

  Microsoft SQL Server Stored procedures [sp_MSSetServerProper
tiesn and sp_MSsetalertinfo] (#NISR03092002A)

From:MICROSOFT <secure_(at)_microsoft.com>
Date:25.07.2002
Subject:Security Bulletin MS02-038: Cumulative Patch for SQL Server 2000 Service Pack 2 (Q316333)

-----BEGIN PGP SIGNED MESSAGE-----

- ----------------------------------------------------------------------
Title:      Cumulative Patch for SQL Server 2000 Service Pack 2
           (Q316333)
Date:       24 July 2002
Software:   Microsoft SQL Server 2000, Microsoft Desktop Engine
           (MSDE) 2000
Impact:     Two vulnerabilities, both of which could enable an
           attacker to run code on the server.
Max Risk:   Moderate
Bulletin:   MS02-038

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

Issue:
======
This patch eliminates two newly discovered vulnerabilities affecting
SQL Server 2000 and MSDE 2000:

- A buffer overrun vulnerability that occurs in several Database
  Consistency Checkers (DBCCs) that ship as part of SQL Server 2000.
  DBCCs are command console utilities that allow maintenance and
  other operations to be performed on a SQL Server. While many of
  these are executable only by sysadmin, some are executable by
  members of the db_owner and db_ddladmin roles as well. In the most
  serious case, exploiting this vulnerability would enable an
  attacker to run code in the context of the SQL Server service,
  thereby giving the attacker complete control over all databases
  on the server.

- A SQL injection vulnerability that occurs in two stored
  procedures used in database replication. One of these can only be
  run by users who have been assigned the db_owner role; the other,
  due to a permissions error, could be run by any user who could log
  onto the server interactively. Exploiting the vulnerability could
  enable an attacker to run operating system commands on the server,
  but is subject to significant mitigating factors as discussed
  below.

Mitigating Factors:
====================
Buffer Overrun Vulnerability in Database Consistency Checkers:

- Both the db_owner and db_ddladmin roles carry with them
  significant privileges, and only should be granted to trusted
  users.

- This allows the user to escalate privileges to the level of the
  service account. And this escalation would be minimal if best
  practices were followed and SQL were installed as a normal domain
  account.

SQL Injection Vulnerability in Replication Stored Procedures:

- Exploiting the vulnerability would, at a minimum, require that
  the attacker have the ability to log onto the server
  interactively. However, best practices strongly militate against
  giving such permissions to untrusted users.

- Simply being able to run the affected stored procedures would not
  enable an attacker to exploit the vulnerability. As discussed in
  the FAQ, the vulnerability could only be exploited if the
  administrator had previously enabled the SQL Server Agent Proxy
  account. By default, this account is disabled.

- Even when enabled, the SQL Server Agent Proxy account has by
  default only the privileges associated with a domain user. If
  administrators follow best practices, it is likely that any user
  who could exploit the vulnerability would already have this level
  of privilege.

Risk Rating:
============
- Internet systems: Moderate
- Intranet systems: Moderate
- Client systems:   None

Patch Availability:
===================
- A patch is available to fix this vulnerability. Please read the
  Security Bulletin at
  http://www.microsoft.com/technet/security/bulletin/ms02-038.asp
  for information on obtaining this patch.

Acknowledgment:
===============
- Cesar Cerrudo

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

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.

-----BEGIN PGP SIGNATURE-----
Version: PGP 7.1

iQEVAwUBPT80d40ZSRQxA/UrAQGmUwf/T/2sIhvrwxbeQOxZxxyllnUo70DyScuW
zafKqyiMtpeQd9vilQdzvOke+ywyFUENZalxwCrTlrmfmKDTP928oOR08a4vXZKa
s6eASOM9LhpGsbXx+tYiu/hxfdJmGHzXnsKIKVeBSdwFloUT3DdcmFtBMOP8REg0
mrVsyv41nnSqtwOKJq0AxIn3f/cTK4FVfmUBUfDpkByAgvNfy6gFsO5avuRplX9v
fWdksv+BdgVCf03IqPOXerj8UkNOW+oKpmSfx66Q+bpB9YbhWazJmU2fKs9Vth20
yw3XB9O7ou3264d4UcJPoHmWcvMFNuWrJfhGmGzlvSnLIp/IFZgMOg==
=Fi4E
-----END PGP SIGNATURE-----



*******************************************************************

You have received this e-mail bulletin because of your subscription to the
Microsoft Product Security Notification Service.  For more information on this
service, please visit http://www.microsoft.com/technet/security/notify.asp.

To verify the digital signature on this bulletin, please download our PGP key
at http://www.microsoft.com/technet/security/notify.asp.

To unsubscribe from the Microsoft Security Notification Service, please visit
the Microsoft Profile Center at http://register.microsoft.com/regsys/pic.asp

If you do not wish to use Microsoft Passport, you can unsubscribe from the
Microsoft Security Notification Service via email as described below:
Send an email to unsubscribe to the Service by following these steps:
a. Send an e-mail to [email protected] The subject line and the message
body are not used to process the subscription request, and can be anything you
like.
b. Send the e-mail.
c. You will receive a response, asking you to verify that you really want to
cancel your subscription. Compose a reply, and put "OK" in the message body.
(Without the quotes). Send the reply.
d. You will receive an e-mail telling you that your name has been removed from
the subscriber list.

For security-related information about Microsoft products, please visit the
Microsoft Security Advisor web site at http://www.microsoft.com/security.

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