Lucene search

K
securityvulnsSecurityvulnsSECURITYVULNS:DOC:271
HistoryMay 31, 2000 - 12:00 a.m.

Security Bulletin (MS00-035)

2000-05-3100:00:00
vulners.com
61

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

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.

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.