Skipfish a Web Application Security Scanner from Google
Google has released a Web Application Security Scanner over at Google Code. This can be used to scan you site for possible security issues which might be lurking around. Skipfish prepares an interactive site-map for the targeted site by carrying out a recursive crawl and dictionary-based probes.
This scanner is easy to setup on an Ubuntu machine. You’ll need to have the packages for gcc and make installed on your system in order to compile Skipfish from it’s sources. Once you install these, download the Skipfish package from the project download page. Once you download it, unzip the files to a folder of it’s own and head over to that folder in your terminal window and issue a make command by just entering this in the terminal.
make |
After the package compiles you can test to see if it was successful by issuing the following command in the terminal
./skipfish -h |
This should show you a the Skipfish help screen. If you don’t get that, check the make output to see if there were any errors during the compile process.
Once you get Skipfish compiled and ready on your system, head over to their documentation pages to learn more on how to use this to tool to scan your site.
This tool creates a html report of the scan in the output directory you specify and the output looks like this:
Skipfish has a highly optimized HTTP handling which allows you to achieve up to 2000 requests per second on servers which can take that load. It also doesn’t depend on the technology you use to host and build your web application.
If you’re interested in what types of scans are currently implemented on this tool, here’s what it supports (from their documentation page):
- High risk flaws (potentially leading to system compromise):
- Server-side SQL injection (including blind vectors, numerical parameters).
- Explicit SQL-like syntax in GET or POST parameters.
- Server-side shell command injection (including blind vectors).
- Server-side XML / XPath injection (including blind vectors).
- Format string vulnerabilities.
- Integer overflow vulnerabilities.
- Medium risk flaws (potentially leading to data compromise)
- Stored and reflected XSS vectors in document body (minimal JS XSS support present).
- Stored and reflected XSS vectors via HTTP redirects.
- Stored and reflected XSS vectors via HTTP header splitting.
- Directory traversal (including constrained vectors).
- Assorted file POIs (server-side sources, configs, etc).
- Attacker-supplied script and CSS inclusion vectors (stored and reflected).
- External untrusted script and CSS inclusion vectors.
- Mixed content problems on script and CSS resources (optional).
- Incorrect or missing MIME types on renderables.
- Generic MIME types on renderables.
- Incorrect or missing charsets on renderables.
- Conflicting MIME / charset info on renderables.
- Bad caching directives on cookie setting responses.
- Low risk issues (limited impact or low specificity):
- Directory listing bypass vectors.
- Redirection to attacker-supplied URLs (stored and reflected).
- Attacker-supplied embedded content (stored and reflected).
- External untrusted embedded content.
- Mixed content on non-scriptable subresources (optional).
- HTTP credentials in URLs.
- Expired or not-yet-valid SSL certificates.
- HTML forms with no XSRF protection.
- Self-signed SSL certificates.
- SSL certificate host name mismatches.
- Bad caching directives on less sensitive content.
- Internal warnings:
- Failed resource fetch attempts.
- Exceeded crawl limits.
- Failed 404 behavior checks.
- IPS filtering detected.
- Unexpected response variations.
- Seemingly misclassified crawl nodes.
- Non-specific informational entries:
- General SSL certificate information.
- Significantly changing HTTP cookies.
- Changing Server, Via, or X-... headers.
- New 404 signatures.
- Resources that cannot be accessed.
- Resources requiring HTTP authentication.
- Broken links.
- Server errors.
- All external links not classified otherwise (optional).
- All external e-mails (optional).
- All external URL redirectors (optional).
- Links to unknown protocols.
- Form fields that could not be autocompleted.
- All HTML forms detected.
- Password entry forms (for external brute-force).
- Numerical file names (for external brute-force).
- User-supplied links otherwise rendered on a page.
- Incorrect or missing MIME type on less significant content.
- Generic MIME type on less significant content.
- Incorrect or missing charset on less significant content.
- Conflicting MIME / charset information on less significant content.
- OGNL-like parameter passing conventions.
You can get more information about Skipfish and download it from their project site on Google Code.
Links:
Skipfish Project on Google Code
Skipfish Documentation
Skipfish Downloads





![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=ed061bbe-dd0c-4417-b397-2e0af2360c8a)


![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=35b4c19a-ab11-4dd0-a5a0-6312581fa140)

![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=92b7c575-bfa2-468c-a1e1-f95eb7be1034)

![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=7580011b-9f43-4032-8603-8727a1413e46)








![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=c9962636-6046-4b8c-a4cb-8cbc2a5398bc)

![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=172b8fae-3367-46a0-b2cb-8d87937ce456)
Web developers have to check out Google’s new Firefox + Firebug addon called Page Speed. This addon inspects your webpage to see how you can optimize the load time. Yahoo’s YSlow was good, but Google takes it a few steps further to even inspect your html and styles to see what can hider the render time of the page once it’s loaded.




One cool functionality in Tweets60 is that you can configure multiple access points and prioritize them. Useful when you’ve got Wifi access and then default to GPRS/3G connection when you’re not in Wifi range. If you’re on a tight data plan, this application also comes with an option to save your bandwidth by allowing you to set the refresh frequency to manual or set it to 5, 10 or 30 minutes.![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=fb4013d7-3b4d-462e-9245-0179eaff74d5)
