The information in this article applies to:
SYMPTOMSA malicious user may be able to cause a different program to run in place of Rasman. Significantly, this program would run in the System context and allow the program to take almost any action on the computer. CAUSEThis behavior occurs because the security descriptor that secures the Rasman.exe file contains inappropriate Access Control Entries (ACEs) in its Discretionary Access Control List (DACL). The incorrect ACE could allow an unprivileged user to change Rasman's operating parameters (including the location of the Rasman executable file) using Service Control Manager. RESOLUTIONMicrosoft has released a tool to reset the permissions to the appropriate value. Windows NT 4.0A supported fix that corrects this problem is now available from Microsoft, but has not been fully regression tested and should be applied only to systems determined to be at risk of attack. Please evaluate your system's physical accessibility, network and Internet connectivity, and other factors to determine the degree of risk to your system. If your system is sufficiently at risk, Microsoft recommends you apply this fix. Otherwise, wait for the next Windows NT 4.0 service pack service pack that contains this fix.To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web: http://www.microsoft.com/support/supportnet/overview/overview.aspThis hotfix has been posted to the following Internet location as Fixrasi.exe (x86) and Fixrasa.exe (Alpha): ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/nt40/Hotfixes-PostSP6/Security/Rasman-fix/NOTE: If you run this file on a computer that cannot connect to the IPC$ share on the remote computer or if the credentials of the logged on user do not have administrative privileges on the remote computer, you may receive an error message stating that RasMan was not fixed. Terminal Server EditionA supported fix that corrects this problem is now available from Microsoft, but has not been fully regression tested and should be applied only to systems determined to be at risk of attack. Please evaluate your system's physical accessibility, network and Internet connectivity, and other factors to determine the degree of risk to your system. If your system is sufficiently at risk, Microsoft recommends you apply this fix. Otherwise, wait for the next Windows NT 4.0, Terminal Server Edition service pack service pack that contains this fix.To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web: http://www.microsoft.com/support/supportnet/overview/overview.aspThis hotfix has been posted to the following Internet location as Fixrasi.exe (x86) and Fixrasa.exe (Alpha): ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/nt40/Hotfixes-PostSP6/Security/Rasman-fix/NOTE: The files in the above folder run on Windows NT Server 4.0, Terminal Server Edition, too. NOTE: If you run this file on a computer that cannot connect to the IPC$ share on the remote computer or if the credentials of the logged on user do not have administrative privileges on the remote computer, you may receive an error message stating that RasMan was not fixed. STATUSMicrosoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. MORE INFORMATION
You can use the Rasman tool to manage dial-up connections. The vulnerability has nothing to do with Rasman itself; the vulnerability occurs because there is an opportunity for a malicious user to cause other code to run in place of Rasman.
http://www.microsoft.com/security/bulletins/ms99-041.aspFor additional security-related information about Microsoft products, please visit the following Microsoft Web site: http://www.microsoft.com/security/ Additional query words:
Keywords : ntras ntdomain ntsecurity ntsp kbbug4.00 kbfix4.00 |
Last Reviewed: October 27, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |