-----BEGIN PGP SIGNED MESSAGE----- Microsoft Security Bulletin (MS00-035) - -------------------------------------- Patch Available for "SQL Server 7.0 Service Pack Password" Vulnerability Originally posted: May 30, 2000 Updated: June 15, 2000 Summary ======= On May 30, 2000, Microsoft released the original version of this bulletin, to announce the availability of 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. On June 15, 2000, the bulletin was updated to note that, under the same conditions as originally reported, the password also is recorded in a second file. A new version of the patch is available that prevents the password from being recorded in either file. 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 files %TEMP%\sqlsp.log and %WINNT%\setup.iss. The default permissions on the files would allow any user to read them 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 (KB) article Q263968, http://www.microsoft.com/technet/support/kb.asp?ID=263968 - 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 the following customers for working with us to protect customers: - Gordon Newman of PeopleSoft for reporting the presence of the password in sqlsp.log - Akintunde Oluwaleimu for reporting the presence of the password in setup.iss Revisions ========= - May 30, 2000: Bulletin Created. - June 15, 2000: Bulletin updated to discuss password presence in setup.iss. - ------------------------------------------------------------------- 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 June 15,2000 (c) 2000 Microsoft Corporation. All rights reserved. Terms of use -----BEGIN PGP SIGNATURE----- Version: PGP 6.0.2 iQEVAwUBOUkgn40ZSRQxA/UrAQFX3wgAk3qJLfG9c3aeXuhZU6KbfnR1bnu3/6oD VBh9wpjPLSfznG/HU2SHxEfFp19A6TK/VdXs9RFl9l0Vf5TMOmHS2jWhxZ3QwQwP e/B6IFFtaOd/wPb59C9esZ5iC7D1A7Q0jdtYGMuc9J5mTa/GFlA4/KwvVc3Xzs/B FSHQvxSStu9b9MzFLWePfsYNbyqnTyawqSjZ3nKPplwBQieRE/UG7Y2imhl6Y4M2 cRqB7VihBoqblbcKZaodYcuhztCxI2+UfSR5Cw9l5outrYnupRztrXuqY5u2/r7J LtZuU7iqOb/X9IeDEugjxgCDzPJDetGqVZ2n2EZDrxCAreayLKqBJw== =kuLw -----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.