 |
 |
|
September 28, 2006Static code analysis for web appsOver at Security Compass they have released "Securitycompass Web Application Analysis Tool", or SWAAT for short. It is a FREE static code analysis tool that will parse PHP, ASP and JSP files, looking for possible coding defects in the code. I downloaded it and gave it a try on my ASP.NET 2.0 directories, and it couldn't pick them up at all. Checking their FAQ it says it supports .NET 1.1 or above... but I am thinking they mean ASP, and NOT ASP.NET. You may have better results. If you are a PHP developer you may have better results. It looks like from their examples that this was what the tool was originally targeting for. It is in beta, and I caused a bunch of exceptions just trying to run it. ie: You have to run swaat.exe from their base directory, you can't call it with an explicit path, as it fails with an IO exception.... not being able to load the XML files. It is a beta, so I won't be to critical on that at this point. You can download SWAAT here and give it a try. You might have better results than I did. Posted by SilverStr at September 28, 2006 08:48 AM | TrackBackComments
Well, I'm not impressed. It flags a require_once call in PHP as a medium security risk.... ALL require_once calls! And when I ran it on one of my large include directories, it spits out an exception: Unhandled Exception: System.IndexOutOfRangeException: Index was outside the boun Not really helpful. Posted by: Mike Weller at September 29, 2006 03:15 AMHi, It looks like three major bugs have been reported is crashing on excessive "&" in the files, trailing slash causing the application to crash and lastly that swaat has to be run from its home directory only as it is looking for the xml files. That being said in response to your statement about .NET 1.1 and above supported is closer to the statement in terms of requirements for SWAAT as it is written in .NET. The code it audits is ASP.NET, hopefully in the next release we will attempt to start with C# etc. Lastly to address Mike's comment about require_once, As far as i can tell we don't look for require_once. It is a free tool that looks for functions (which can be added / delete by modifying asp.xml, jsp.xml & php.xml) that if used improperly could lead to web application vulnerabilities. It is supposed to aid auditors, developers etc. I do realize that this release has too many findings which we are planning to address by doing some variable tracking etc. If there are other problems / suggestions for improvement you would have, please send me an email directly at my above email address or to swaat@securitycompass.com and we would be happy to integrate it into the tool. Thanks Nish. Post a comment
|
 
My 5 Favorite Books
Writing Secure Code
Secure Programming Cookbook Security Engineering Secure Coding Principles & Practice Inside the Security Mind
My 5 Favorite Papers
Smashing the Stack
Penetration Studies Covert Channel Analysis of Trusted Systems DoD Trusted Computer System Evaluation Criteria NSA Security Recommendation Guides
Archives
September 2006
August 2006 July 2006 June 2006 May 2006 April 2006 March 2006 February 2006 January 2006 December 2005 November 2005 October 2005 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 April 2003 March 2003 February 2003 January 2003 December 2002 November 2002 October 2002 September 2002 August 2002 July 2002 |
|
