19.04.2013 Views

2KKUU7ita

2KKUU7ita

2KKUU7ita

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 11: Windows<br />

Windows XP SP2 and later versions, as well as Windows Server 2003 SP1 and<br />

later versions, have a new “undocumented feature” that can (and will)<br />

severely limit your network scanning speeds: Only ten half-open TCP connections<br />

can be made at a time. If you think your system might be affected by this,<br />

check out the Event ID 4226 Patcher tool (www.lvllord.de) for a hack to run<br />

on the Windows TCP/IP stack that will allow you to adjust the TCP half-open<br />

connections setting to a more realistic number. The default is to change it to<br />

50, which seems to work well.<br />

Be forewarned that Microsoft doesn’t support this hack. Having said that, I<br />

haven’t had any trouble with this hack at all. Disabling the Windows Firewall<br />

(or other third-party firewall) can help speed things up, too. If possible, test<br />

on a dedicated system or virtual machine, because doing so minimizes any<br />

impact your test results may have on the other work you do on your computer.<br />

Gathering Information about Your<br />

Windows Vulnerabilities<br />

When you assess Windows vulnerabilities, start by scanning your computers<br />

to see what the bad guys can see.<br />

The exploits in this chapter were run against Windows from inside a firewall.<br />

Unless I point out otherwise, all the tests in this chapter can be run against all<br />

versions of the Windows OS. The attacks in this chapter are significant enough<br />

to warrant testing for, regardless of your current setup. Your results might<br />

vary from mine depending on the specific version of Windows, patch levels,<br />

and other system hardening you’ve done.<br />

System scanning<br />

A few straightforward processes can identify weaknesses in Windows systems.<br />

Testing<br />

Start gathering information about your Windows systems by running an initial<br />

port scan:<br />

1. Run basic scans to find which ports are open on each Windows system:<br />

Scan for TCP ports with a port scanning tool, such as NetScanTools Pro.<br />

The NetScanTools Pro results in Figure 11-1 show several potentially<br />

vulnerable ports open on a Windows 7 system, including those for DNS<br />

(UDP port 53); the ever-popular — and easily hacked — NetBIOS (port<br />

139); and SQL Server (UDP 1434).<br />

203

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!