Scathing report in XP SP2 security

ainwood

Consultant.
Administrator
Moderator
Joined
Oct 5, 2001
Messages
30,080
Intro:
Reg Review We evaluated the security features of Windows XP SP2 on a test machine, following a clean install of XP Pro with no configuration changes and no third-party software or drivers installed. We installed XP with the NTFS file system, choosing all of the factory defaults, then patched it with each recommended security update including SP-1 (required), before installing SP2.

While we found that there are indeed a few minor improvements worthy of acknowledgment, in particular, some rather low-level improvements that don't show to the admin or user, overall, SP2 did little to improve our system's practical security, leaving too many services and networking components enabled, bungling permissions, leaving IE and OE vulnerable to malicious scripts, and installing a packet filter that lacks a capacity for egress filtering.

The new Security Center utility with its frequent Security Alert popups will certainly give users the impression that SP2 is a security-oriented package, as Microsoft's PR boilerplate promises. However, The Security Center does little beyond warning users that the firewall is disabled, that automatic updating is disabled, or that antivirus software has not been installed. It may look impressive, but the SP2 package fails to provide several of the most important, basic modifications required to run Windows safely on an Internet-connected machine.

Read the ful article here.
 
Remote Procedure Call (RPC), automatic. This is one of Microsoft's greatest security holes. RPC enables one machine to execute code remotely on another. On UBIX/BSD/Linux, it can be disabled safely. On Windows, it cannot be disabled, as MS has made a plethora of necessary services dependent on it. It's a huge security hole that simply cannot be avoided. It must be blocked by a firewall.

Additionally, DCOM (Distributed COM) is enabled by default. It is unnecessary on most home machines, and should be disabled unless needed. It's the component that the Blaster worm exploited to get at RPC.
And what do we learn here? Never plug an unconfigured Windows XP without a firewall to the Internet! The amount of security flaws is simply appalling. :mad:
 
crystal said:
And what do we learn here? Never plug an unconfigured Windows XP without a firewall to the Internet! The amount of security flaws is simply appalling. :mad:

Hmm, might be a good idea to install one now. Anyone know where I can get a free firewall(besides outpost. My computer doesn't like it for some reason)
 
Steve Gibson (GRC) would love this article. Dead-on. He's been yelling and ranting about Windows' numerous unnecessary and exploit-ridden services that boot-up by default. He says that Messenger spam wouldn't be that big, DCOM troubles would have been eliminated, and buffer overrun problems with UPnP would have never occured had they been disabled by default.

:lol: That link article was written by Thomas C. Greene, a writer that Gibson fought with when Greene interviewed Microsoft about socket locking. Gibson said that Green was misrepresenting his points and case and all...
 
Have you noticed any difficulties playing multiplayer conquests on a LAN after installing SP2?
 
Back
Top Bottom