Microsoft Security Bulletin MS03-031: Cumulative Patch for Microsoft SQL Server (Q815495)

2003-07-24T00:00:00
ID SECURITYVULNS:DOC:4890
Type securityvulns
Reporter Securityvulns
Modified 2003-07-24T00:00:00

Description

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


Title: Cumulative Patch for Microsoft SQL Server (815495)

Date: 23 July 2003 Software:
- Microsoft SQL Server 7.0 - Microsoft Data Engine (MSDE) 1.0 - Microsoft SQL Server 2000 - Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) - Microsoft SQL Server 2000 Desktop Engine (Windows)

Impact: Run code of attacker's choice Max Risk: Important Bulletin: MS03-031

Microsoft encourages customers to review the Security Bulletins at: http://www.microsoft.com/technet/security/bulletin/MS03-031.asp http://www.microsoft.com/security/security_bulletins/ms03-031.asp


Issue:

This is a cumulative patch that includes the functionality of all previously released patches for SQL Server 7.0, SQL Server 2000, MSDE 1.0, and MSDE 2000. In addition, it eliminates three newly discovered vulnerabilities.

  • Named Pipe Hijacking - Upon system startup, SQL Server creates and listens on a specific named pipe for incoming connections to the server. A named pipe is a specifically named one-way or two-way channel for communication between a pipe server and one or more pipe clients. The named pipe is checked for verification of which connection attempts can log on to the system running SQL Server to execute queries against data that is stored on the server.

A flaw exists in the checking method for the named pipe that could allow an attacker local to the system running SQL Server to hijack (gain control of) the named pipe during another client's authenticated logon password. This would allow the attacker to gain control of the named pipe at the same permission level as the user who is attempting to connect. If the user who is attempting to connect remotely has a higher level of permissions than the attacker, the attacker will assume those rights when the named pipe is compromised.

  • Named Pipe Denial of Service - In the same named pipes scenario that is mentioned in the "Named Pipe Hijacking" section of this bulletin, it is possible for an unauthenticated user who is local to the intranet to send a very large packet to a specific named pipe on which the system running SQL Server is listening and cause it to become unresponsive.

This vulnerability would not allow an attacker to run arbitrary code or elevate their permissions, but it may still be possible for a denial of service condition to exist that would require that the server be restarted to restore functionality.

  • SQL Server Buffer Overrun - A flaw exists in a specific Windows function that may allow an authenticated user-with direct access to log on to the system running SQL Server-the ability create a specially crafted packet that, when sent to the listening local procedure call (LPC) port of the system, could cause a buffer overrun. If successfully exploited, this could allow a user with limited permissions on the system to elevate their permissions to the level of the SQL Server service account, or cause arbitrary code to run.

Mitigating Factors:

Named Pipe Hijacking: - To exploit this flaw, the attacker would need to be an authenticated user local to the system. - This vulnerability provides no way for an attacker to remotely usurp control over the named pipe.

Named Pipe Denial of Service: - Although it is unnecessary that the attacker be authenticated, to exploit this flaw the attacker would require access to the local intranet. - Restarting the SQL Server Service will reinstate normal operations - This flaw provides no method by which an attacker can gain access to the system or information contained in the database.

SQL Server Buffer Overrun: - To exploit this flaw, the attacker would need to be an authenticated user local to the system. - This vulnerability cannot be remotely exploited.

Risk Rating:

  • Important

Patch Availability:

  • A patch is available to fix this vulnerability. Please read the Security Bulletins at http://www.microsoft.com/technet/security/bulletin/ms03-031.asp http://www.microsoft.com/security/security_bulletins/ms03-031.asp

for information on obtaining this patch.

Acknowledgment:

  • Andreas Junestam www.@stake.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.

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

iQEVAwUBPx4VXo0ZSRQxA/UrAQHu1wf9G26FlGldouwnEiqGzxCdd7kgtaMZ0Tgy FDF5gsWpZW4klHjBVz4yUm20ukJsOp5+b1kcLATcJyTwv5Cd4F2JPRXBKTcS6mZO DQlYxd6ylA+td9TXLJWlgU6Ffji5ENdx7LUv5DchkuOMH/wyCpwVFlfZom2d6kte apHQiRh8RPrIOoIRcp7cj+20IhBNL7fxhHUh1otLlR0mZUT56rD4e99XnytStCN3 NEzPZoXQMN5uhIkbgYK3JwmyjBR8gjL+Dks5zuzZ9AQ4laHmPubk1grYBn/BjxwY NjzKIaJ6IOmER/kTMFwdVLUpCzsAK6xD6GJLkVbJRJvQTQF1M2d6Aw== =NL9z -----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: Reply to this message with the word UNSUBSCRIBE in the Subject line.

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