News

RPC Vulnerability Affects NT, W2K, XP

Microsoft on Wednesday warned users of an "important" new vulnerability involving the Remote Procedure Call (RPC) protocol in Windows NT, Windows 2000 and Windows XP that can allow a denial-of-service attack.

While a patch is available for Windows 2000 and Windows XP, Redmond cited architectural issues as preventing the company from creating a patch for Windows NT 4.0. The company provided workaround instructions, instead, for NT customers in the bulletin (www.microsoft.com/technet/security/bulletin/MS03-010.asp).

Microsoft's bulletin said servers on an intranet were the most likely to be vulnerable to the attack. The company went further to suggest that responsible network security practices should prevent the vulnerability from being open on Internet servers. "Best practices recommend blocking all TCP/IP ports that are not actually being used," the bulletin stated. "For this reason, most machines attached to the Internet should have port 135 blocked. RPC over TCP is not intended to be used in hostile environments such as the Internet."

The bulletin is Microsoft's 10th of 2003.

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