[15120] in bugtraq
Microsoft Security Bulletin (MS00-035)
daemon@ATHENA.MIT.EDU (Microsoft Product Security)
Wed May 31 22:03:05 2000
Message-Id: <D1A11CCE78ADD111A35500805FD43F5867C2FE@RED-MSG-04>
Date: Tue, 30 May 2000 13:09:56 -0700
Reply-To: Microsoft Product Security <secnotif@MICROSOFT.COM>
From: Microsoft Product Security <secnotif@MICROSOFT.COM>
X-To: MICROSOFT_SECURITY@ANNOUNCE.MICROSOFT.COM
To: BUGTRAQ@SECURITYFOCUS.COM
The following is a Security Bulletin from the Microsoft Product Security
Notification Service.
Please do not reply to this message, as it was sent from an unattended
mailbox.
********************************
-----BEGIN PGP SIGNED MESSAGE-----
Microsoft Security Bulletin (MS00-035)
- --------------------------------------
Patch Available for "SQL Server 7.0 Service Pack Password"
Vulnerability
May 30, 2000
Summary
=======
Microsoft has released a patch that eliminates a security
vulnerability in Microsoft(r) SQL Server(r) 7.0 Service Packs 1 and 2
installation routine. When run on a machine that is configured in a
non-recommended mode, the routines record the administrator password
in a log file, where it could be read by any user who could log onto
the server at the keyboard.
Frequently asked questions regarding this vulnerability and
the patch can be found at
http://www.microsoft.com/technet/security/bulletin/fq00-035.asp
Issue
=====
When SQL Server 7.0 Service Packs 1 or 2 are installed on a machine
that is configured to perform authentication using Mixed Mode, the
password for the SQL Server standard security System Administrator
(sa) account is recorded in plaintext in the file \%TEMP%\sqlsp.log.
The default permissions on the file would allow any user to read it
who could log onto the server interactively.
The password is only recorded if Mixed Mode is used, and even then,
only if the adminstrator chose to use SQL Server Authentication when
installing the service pack. Microsoft has long recommended that SQL
servers be configured to use the more secure Windows NT Authentication
Mode, and customers who have followed this recommendation would not be
affected. Even on affected machines, the password could not be
compromised if, per normal security recommendations, normal users are
prevented from logging onto the machine interactively.
Affected Software Versions
==========================
- Microsoft SQL Server 7.0 Service Packs 1 and 2
Patch Availability
==================
- Microsoft SQL Server 7.0 Service Pack 2:
http://www.microsoft.com/Downloads/Release.asp?ReleaseID=21546
Note: Additional security patches are available at the Microsoft
Download Center
More Information
================
Please see the following references for more information related to
this issue.
- Frequently Asked Questions: Microsoft Security Bulletin MS00-035,
http://www.microsoft.com/technet/security/bulletin/fq00-035.asp
- Microsoft Knowledge Base article Q263968 discusses this issue
and will be available soon.
- Microsoft SQL Server 7.0 Security,
http://www.microsoft.com/technet/SQL/Technote/secure.asp.
- Microsoft TechNet Security web site,
http://www.microsoft.com/technet/security/default.asp
Obtaining Support on this Issue
===============================
This is a fully supported patch. Information on contacting Microsoft
Technical Support is available at
http://support.microsoft.com/support/contact/default.asp.
Acknowledgments
===============
Microsoft thanks Gordon Newman of PeopleSoft for reporting this issue
to us and working with us to protect customers.
Revisions
=========
- May 30, 2000: Bulletin Created.
- --------------------------------------------------------
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.
Last Updated May 30,2000
(c) 2000 Microsoft Corporation. All rights reserved. Terms of use.
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.0.2
iQEVAwUBOTQgE40ZSRQxA/UrAQG1Vgf7BAd6NzQUaaOLPtEc3yLvwglJp5tZeNlj
Q9Z5K0e5kPgcuD+gKrKbpIqx9WtXmBMJuE6oEy2Qk+QGC3tBsPX8pDNBfQktAhep
2F2HY4wYG7b6WueTS/zx6udEOfPp9CXoOsCduVGlqU7RptB6FA7rF72sXtXjDyWv
pCCwzdNu8VO7euzwEO9GxxMUPCCq7jSCFH7HrbDLukVgsaoAoZdUwioD4DTx936c
aEmOa5gEyhew0WkeUC1N+X89An24jlbm9hkXbu5KJ0M/f5Nz0iuTNlugMQsiERnX
j9XW106WvwISDdDD4aVotB2uSxp/ZhXhQW8j/2XFLoqesw6X99zr+Q==
=efyX
-----END PGP SIGNATURE-----
*******************************************************************
You have received this e-mail bulletin as a result of your registration
to the Microsoft Product Security Notification Service. You may
unsubscribe from this e-mail notification service at any time by sending
an e-mail to MICROSOFT_SECURITY-SIGNOFF-REQUEST@ANNOUNCE.MICROSOFT.COM
The subject line and message body are not used in processing the request,
and can be anything you like.
To verify the digital signature on this bulletin, please download our PGP
key at http://www.microsoft.com/technet/security/notify.asp.
For more information on the Microsoft Security Notification Service
please visit http://www.microsoft.com/technet/security/notify.asp. For
security-related information about Microsoft products, please visit the
Microsoft Security Advisor web site at http://www.microsoft.com/security.
