Today’s example is about what happens when a login page is loaded securely, albeit embedded within an insecure page. This is a common security anti-pattern and you’ll see it on many sites. The example in the video is from Countdown in New Zealand but again, there are countless others out there. Take a look at the video then I’ll come back to how I mounted the attack:

Make sense? In short, you can never trust the HTTP component of the communication and without the ability to see the URL in the browser loaded over an HTTPS address with a valid certificate, the SSL implementation is almost useless.

The mechanics of how I’ve demonstrated attacks against insufficient use of SSL involves using Fiddler script. Many of you may already be familiar with Fiddler, the scripting option gives us the ability to manipulate unencrypted traffic on the wire just as an attacker might at any point in the network communication. Clearly an attacker at, say an ISP or running a rogue wireless hotspot wouldn’t be running Fiddler, but the mechanics of manipulating requests and responses is similar with other tools.

In this example I simply added the following script in the OnBeforeResponse event:

if (oSession.HostnameIs("www.countdown.co.nz") && oSession.PathAndQuery=="/") {// Remove any compression or chunkingoSession.utilDecodeResponse();