Web Informant #326, 25 April 2003: Anatomy of a hack
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
After my last column on problems with SBC's Web hosting, I asked Caleb Sima from SPI Dynamics, a Web application and security assessment software firm, to give me some insights about breaking into Web sites. Caleb has a pretty cool job: He gets paid to do this, in the process demonstrating the need for tools such as his employer sells as well as the various weaknesses of people's sites. When he visited me at CMP last fall, he was inside our own Web site and reading stuff that he shouldn't have had access to within a minute or so. Fortunately, our Web folks have tightened things up, but you may not be so lucky.
I asked Caleb to give me an idea of how he manages to find these vulnerabilities so quickly, and he came up with a few suggestions. If you understand how Web servers work and how they have directory structures and input forms just like your computer on your desktop, you can get pretty far -- even without much other specialized knowledge. To give you a flavor of this, I submit his prescription for locating a Web application attack vulnerability called cross-site scripting.
Here are the steps to see if your Web applications are vulnerable to XSS attacks:
Step 1. Open any Web site in a browser, and look for places on the site that accept user input such as a search form or some kind of login page. Enter the word test in the search box and send this to the Web server.
Step 2. Look for the Web server to respond back with a page similar to something like "Your search for 'test' did not find any items" or "Invalid login test." If the word 'test' appears in the results page, you are in luck.
Step 3. To test for XSS, input the string "<script>alert('hello')</script>" without the quotes in the same search or login box you used before, and send this to your Web server.
Step 4. If the server responds back with a popup box that says "hello", then the Web site or Web application is vulnerable to XSS.
Step 5. If Step 4 fails and the Web site does not return this information, you still might be at risk. Click the 'View|Source' option in your browser so you can see the actual HTML code of the Web page. Now find the <script> string that you sent the server. If you see the entire "<script>alert('hello')</script>" text in this source code, then the Web server is vulnerable to XSS.
If these steps don't make much sense to you, not to worry. You can still get some mileage, particularly when you are in the throes of picking a hosting provider. I suggest that you might want to send them this column and see what kind of response you get from them before you give them your business. If you get no response or a canned response, then you probably should go elsewhere. You could also send this column to your IT department. If they don't understand what I am talking about here, then you might want to bring that to the attention of your CEO and find out why.
There are plenty of other Web site vulnerabilities. Hopefully this will get you motivated to seek them out, either by using SPI Dyanmics' product called WebInspect or someone else's, and by being more diligent about what applications you allow access to your Web content. Here's my article that I wrote earlier this year on this subject for VARBusiness.
Entire contents copyright 2003 by David Strom, Inc.
David Strom, email@example.com, +1 (516) 562-7151
Port Washington, NY 11050
Web Informant is (r) registered trademark with the US PTO
ISSN #1524-6353 registered with U.S. Library of Congress
If you'd like to subscribe (issues are sent via e-mail), please send an e-mail to: Informantfirstname.lastname@example.org?body=subscribe.