Patch Available for 'RDISK Registry Enumeration File' Vulnerability
Published: January 21, 2000 | Updated: February 04, 2000
Version: 1.0
Originally Posted: January 21, 2000 Revised: February 4, 2000
Summary
On January 21, 2000, Microsoft released the original version of this bulletin, discussing a security vulnerability in a Microsoft® Windows NT 4.0 administrative utility. The original version of the bulletin discussed the vulnerability within the context of Windows NT 4.0 Server, Terminal Server Edition. However, we have since learned of scenarios under which the vulnerability could also affect Windows NT 4.0 servers and workstations, and have revised the bulletin accordingly.
The utility creates a temporary file during execution that can contain security-sensitive information, but does not appropriately restrict access to it. Under certain conditions, it could be possible for a malicious user to read the file as it was being created
The RDISK utility is used to create an Emergency Repair Disk (ERD) in order to record machine state information as a contingency against system failure. During execution, RDISK creates a temporary file containing an enumeration of the registry. The ACLs on the file allow global read permission, and as a result, a malicious user who knew that the administrator was running RDISK could open the file and read the registry enumeration information as it was being created. RDISK erases the file upon successful completion, so under normal conditions there would be no lasting vulnerability.
By default, the file is not shared and therefore could not be read by other network users.
Microsoft thanks Arne Vidstrom (https://ntsecurity.nu) for reporting this issue to us and working with us to protect customers.
Revisions
January 21, 2000: Bulletin Created.
February 4, 2000: Bulletin revised to address other affected versions
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.
As an Information Security Administrator, you plan and implement information security of sensitive data by using Microsoft Purview and related services. You’re responsible for mitigating risks by protecting data inside collaboration environments that are managed by Microsoft 365 from internal and external threats and protecting data used by AI services. You also implement information protection, data loss prevention, retention, insider risk management, and manage information security alerts and activities.