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.
********************************
Microsoft Security Bulletin (MS99-036)
--------------------------------------
Windows NT 4.0 Does Not Delete Unattended Installation File
Originally Posted: September 10, 1999
Summary
=======
When an unattended installation of Windows NT 4.0 completes, a copy of the
file that contains installation parameters remains on the hard drive.
Depending on the method that was to perform the installation and the
specific installation parameters that were selected, the file could contain
sensitive information, potentially including the local Administrator
password.
Issue
=====
When an unattended installation of Windows NT 4.0 is performed, the
installation parameters are included in a file named Unattend.txt. A
vulnerability exists because the installation process copies the parameter
file to a file in %windir%\system32 ($winnt$.inf for a normal unattended
installation, or $nt4pre$.inf if Sysprep was used) but does not delete it
when the installation completes. By default, this file can be read by any
user who can perform an interactive logon. If sensitive information such as
account passwords were provided in the installation parameters file, the
information could be compromised.
As discussed in the FAQ, the degree of risk from this vulnerability varies
depending on the particular installation. However, in general, workstations
and terminal servers deployed using the Sysprep tool would be at greatest
risk from it.
Affected Software Versions
==========================
- Microsoft Windows NT Workstation 4.0
- Microsoft Windows NT Server 4.0
- Microsoft Windows NT Server 4.0, Enterprise Edition
- Microsoft Windows NT Server 4.0, Terminal Server Edition
Resolution
==========
Customers performing unattended installations of Windows NT 4.0 should
ensure that they either review the file and erase any sensitive information
such as account information and passwords, or delete the file altogether.
Knowledge Base article Q241048 discusses one way to delete the file, via
the RunOnce registry key.
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.
(c) 1999 Microsoft Corporation. All rights reserved. Terms of Use.
*******************************************************************
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.