« Apache 2.2.16 released | Main | Disabling TLS Renegotiation in Apache »

07/26/2010

Scanning for Unsafe URLs - Update 2

This post is sort of a big deal for me because it is the 300th post to this blog.  I'm happy to have reached this particular milestone and want to thank everyone taking the time to visit it and especially thank all of you who have subscribed to my RSS feeds and who are following the site updates on twitter. Additional milestones reached over the past week include an all-time high 75 subscribers to the blog's RSS feed.  This week, the Techstacks Howto's site should reach it's 10,000th page view since the site launched in September 2009 and sometime in August, this blog should reach it's 100,000th page view since re-launching under TypePad roughly 13 months ago.

Saturday's post about updates to my Tools site briefly touched upon BadUrlChk, which I will now cover in more detail here.

PCI Scanners are now testing for unsafe URLs.  The original "Scanning for Unsafe URLs" post introduced a Perl script, which is still a work in progress, that tests many well known, unsafe URLs that we web site administrators don't necessarily want exposed to the Internet-at-large.  Although I think Perl is really cool and I want to get really good at it, a lot of my scripts make use of additional CPAN modules that many folks don't want to necessarily install on their own personal workstations.  The scripts that I've written in groovy also make use of third-party modules.  The Techstacks Tools site exists as a hosted site for people who just want to run the test without having to worry about installing perl or groovy or any of the third party modules that I like to use.

BadUrlChk is a port of the Perl script from the original article.  The output is the same right now but it is running on Google AppEngine and makes use of the Gaelyk framework and HTTPBuilder.  All you need to do is plug in a URL and the scanner will output success or failure messages.  If you've got a vulnerability reporting that the ColdFusion Administrator console is open and running the tool confirms this, re-run the tool after remediation of the vulnerability.  It should then report that ColdFusion console access fails.

Presently, the script and the hosted version running on the Tools site are not completely ready and should be considered early beta.  You can get a pretty good idea of whether or not a small sample of well known, unsafe URLs are open to the Internet but the tools do not presently handle redirection well nor do they handle Authentication responses from the web server.  I'm still working on that.  Sites that redirect can result in a lot of false positives so I'm working on some false positive handlers as well.  

The nice thing about command line scripts is output is easy to handle.  The trouble with them is that they don't always translate well on a web site.  I'm working to see if there is a better way to display this output.

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a01156fbc6fe6970c013485ae6385970c

Listed below are links to weblogs that reference Scanning for Unsafe URLs - Update 2:

Comments