Having completed my incursion into Metasploiitable 2 I’m beginning my foray into Mutillidae II.
Before starting the manual hands-on stuff I thought I’d throw some automated scanners at the web app for fun and see what results they might generate for me.
Mutillidea version 2.6.5 is hosted on my Windows 7 system using XAMPP and i’m scanning from Kali Linux.
Edge-Security describe ProxyStrike thus:
ProxyStrike is an active Web Application Proxy. It’s a tool designed to find vulnerabilities while browsing an application. It was created because the problems we faced in the pentests of web applications that depends heavily on Javascript, not many web scanners did it good in this stage, so we came with this proxy.
Right now it has available Sql injection and XSS plugins. Both plugins are designed to catch as many vulnerabilities as we can, it’s that why the SQL Injection plugin is a Python port of the great DarkRaver “Sqlibf”.
The process is very simple, ProxyStrike runs like a proxy listening in port 8008 by default, so you have to browse the desired web site setting your browser to use ProxyStrike as a proxy, and ProxyStrike will analyze all the paremeters in background mode. For the user is a passive proxy because you won’t see any different in the behaviour of the application, but in the background is very active.
![:)]()
Some features:
Plugin engine (Create your own plugins!)
Request interceptor
Request diffing
Request repeater
Automatic crawl process
Http request/response history
Request parameter stats
Request parameter values stats
Request url parameter signing and header field signing
Use of an alternate proxy (tor for example ;D )
Sql attacks (plugin)
Server Side Includes (plugin)
Xss attacks (plugin)
Attack logs
Export results to HTML or XML
I didn’t use this tool as a proxy but took advantage of the automated crawl/scan.
I opted for both plugins (SQL attack and XSS & SSI attack) enabled and selected “Crawl using plugins” in the crawler tab.
Watching the log tab during the scan was fascinating as it tries injections.
Navigate to the “Plugins” tab to view discoveries and it’s from here we are able to export these into HTML and XML format.
Sadly the “Export HTML” didn’t work for me and so I resorted to “Export XML” which produced very unwieldy output. The SQL XML results are here and XSS here.
I’m not attempting to exploit any of this information at this point.