News

Microsoft Warns of NT 4.0 Bug

Microsoft Corp. has released a tool that installs tighter permissions on a Windows NT 4.0 registry key. The default permissions could allow a malicious user who can interactively log onto an NT 4.0 machine to compromise the cryptographic keys of other users who subsequently log onto the same machine.

The vulnerability involves a registry key used by the CryptoAPI Base CSPs to specify the driver DLL for a hardware accelerator. By design, such a DLL would have access to users' public and private keys. Although only administrators should have permission to add such a DLL, the permissions on the key actually would allow any user who could interactively log onto the machine to do so. By writing a false DLL and installing it, a malicious user could compromise the keys of other users who subsequently used the machine.

The machines primarily at risk would be workstations and terminal servers. Microsoft Windows NT 4.0 Workstation, NT 4.0 Server, NT 4.0 Server, Enterprise Edition, and NT 4.0 Server, Terminal Server Edition are all affected. Windows 2000 is not affected.

A patch is available for Intel x86 machines at http://www.microsoft.com/Downloads/Release.asp?ReleaseID=20330 and for Compaq Alpha machines at http://www.microsoft.com/Downloads/Release.asp?ReleaseID=20331. - Isaac Slepner

About the Author

Scott Bekker is editor in chief of Redmond Channel Partner magazine.

Featured

  • Microsoft Starting To Roll Out New Excel Connected Data Types

    Microsoft on Thursday announced some Excel and Power BI enhancements that add "connected data types" on top of the standard strings and numbers options.

  • Windows 10 Users Getting New Process for Finding Optional Driver Updates

    Accessing Windows 10 drivers classified as "optional updates" will be more of a manual seek-and-install type of experience, starting on Nov. 5, 2020, Microsoft explained in a Wednesday announcement.

  • Microsoft Changes Privacy Platform Name to SmartNoise

    Microsoft Research has changed the name of its "differential privacy" platform from "WhiteNoise" to "SmartNoise," according to a Wednesday announcement.

  • Why Restarting a Failed SCVMM Job Might Be a Bad Idea

    Occasionally, restarting a failed System Center Virtual Machine Manager job can leave your virtualization infrastructure in an unknown state. Here's how to avoid that.

comments powered by Disqus