Microsoft Monitor: RPC Rips Windows

A Jupiter Research Business Weblog

Jupiter's Microsoft Monitor Research Service helps vendors prepare for market opportunities created by new Microsoft initiatives. In addition, Microsoft Monitor helps business and enterprise users discover which strategies are most successful in dealing with Microsoft and how to best exploit the customer relationship. The Microsoft Monitor Weblog is a companion to Jupiter's Microsoft Monitor Research Service and provides additional news, analysis and insight relevant to the areas most important for Microsoft's growth in both the business and consumer marketplaces. The content on this Weblog is often based on late-breaking events whose sources are deemed to be reliable. The insight and recommendations represent Jupiter's initial analysis. As a result, our positions are subject to refinements or major changes as Jupiter analysts gather more information and perform further analysis. Feedback is welcome at mm@jupitermedia.com.

Contact Us
More information about Jupiter's Microsoft Monitor Research service is available by contacting Kieran Kelly at researchsales@jupitermedia.com or by telephone at 1-800-481-1212

Blogroll
David Card
Michael Gartenberg
Alan Meckler
David Schatsky

Archives
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003

Recent Entries
My PDC Post Morteum
Microsoft Office, the Server Edition, Part Two
Windows Workflow Foundation and Expression
PDC: The Big Day
Windows Vista Sleeper Announcements

July 16, 2003

RPC Rips Windows

This afternoon, Microsoft warned of a "critical" Windows flaw that would allow a hacker to seize control a computer. Windows NT 4, Windows NT 4 Terminal Server, Windows 2000, Windows XP and Windows Server 2003 are all vulnerable to the vulnerability. The flaw is found in the Remote Procedure Call (RPC) protocol, which exposes port 135 to remote access when sent a "specially formed request," according to a Microsoft security alert. This port typically would be exposed on a corporate Intranet, but not necessarily to the Internet.

All businesses should, at the least, make sure that port 135 is closed on all affected Windows PCs. Microsoft also has issued patches for the vulnerable Windows versions. The Windows 2000 patch can be found here and the Windows XP patch here.

Posted by Joe Wilcox at July 16, 2003 03:26 PM