FPNWCLNT.DLL has incorrect checksum |
---|
Risk Level: | High | Check or Attack Name: fpnwclnt checksum |
---|---|---|
Platforms: | Windows NT | |
Description: | The registry key that governs alternate security providers has been altered. If a user has the right to change the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa key, then a DLL file can be installed that allows all password changes to be written to plaintext, or even transmitted off site. Microsoft shipped Windows NT 4.0 Workstation with the Notification Packages registry key set to FPNWCLNT, which allows any user with write permissions to the %systemroot%\system32 directory to insert a DLL that can process password changes. If the FPNWCLNT.DLL file is detected, then its size is verified as the correct size. |
|
Remedy: | Apply the latest Windows NT 4.0 Service Pack, convert to NTFS, verify the ACL allows proper access, and make sure all values for password filter packages are legitimate. Set registry permissions properly. If an unauthorized security provider has been installed, remove FPNWCLNT or validate the FPNWCLNT.DLL. To apply the latest Windows NT 4.0 Service Pack:
—AND— If using a FAT (File Allocation Table) based system, convert to NTFS:
—AND— Restrict permissions on the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa key to be written only by the System and Administrators. WARNING: Incorrectly using Registry Editor may cause severe and irreparable damage and may require you to reinstall your operating system. Internet Security Systems cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. To restrict registry access:
—AND— To verify password filter packages:
If the Notification Packages subkey is present, determine if an unauthorized security provider has been installed. If you detect an unauthorized security provider, then this machine should be considered compromised. If you use FPNW or DSMN, validate the version of FPNWCLNT.DLL dated 05/01/97 at 35,088 bytes. —OR— If you do not use FPNW or DSMN, remove the FPNWCLNT value:
|
|
References: | Microsoft Knowledge Base Article Q99885, Security Issues Occur Due to How WinNT Handles FPNWCLNT.DLL, http://support.microsoft.com/support/kb/articles/q99/8/85.asp |
Know Your Risks |