Free-of-charge white paper informs about the ris... » London: Wherever secure transactions or network access are required, the person requesting access fi... KAICIID joins call by the global community to end ... » In northern Iraq, brutal violence has led to the murder of thousands of innocent civilians. Many rel... Former Army Air Corps pilot helps limbless veteran... » The Gazelle Military Helicopter Trust has been set up to restore Gazelle helicopters that have been ... Best Use of Stop and Search scheme » The Metropolitan Police Service [MPS] welcomes today's further announcement by the Home Secretary re... IPSecurityCenter chosen for Hospital PSIM Project ... » CNL Software has been chosen to provide a comprehensive security management system for a hospital fa... Check Point makes it again as a leader in the Gar... » Check Point has announced that it is again positioned as a Leader in the 2014 Gartner Magic Quadrant... NXT-ID approved for NASDAQ capital market listing » SHELTON, Conn.: NXT-ID, Inc. has announced that its shares of common stock and the warrants to purch... Notting Hill Housing Group chooses Guardian24 to p... » Belfast, UK: One of London’s leading housing associations continues investment in their staff’s pers... Parallels launches Parallels Desktop 10 for Mac ... » LONDON, UK: Parallels has launched Parallels Desktop® 10 for Mac and Parallels Desktop 10 for Mac En... Transactis wins Management Today award for work th... » Consumer insight and anti-fraud company Transactis has been named SME (Small and Medium Enterprise) ...

CLICK HERE TO

Advertise with Vigilance

Got News?

Got news for Vigilance?

Have you got news/articles for us? We welcome news stories and articles from security experts, intelligence analysts, industry players, security correspondents in the main stream media and our numerous readers across the globe.

READ MORE

Subscribe to Vigilance Weekly

Information Security Header

Many recognise that the internet is an insecure place to be, but sometimes the browser itself can heighten this likelihood. In his latest blog post, Jonathan Kuskos WhiteHat's A-Team Application Security Engineer, warns to the danger of an unconventional attack in Firefox (versions 21 and below) - Cross Site Request Forgery.

In his commentary, Jonathan:

Explains ‘Cross Site Request Forgery’

Explains ‘verb tampering’

Uses examples to show how this attack works

Warns that, while Firefox 22 has been patched, previous versions remain vulnerable - highlighting the issue that users should update browsers to remain secure

 

It appears that an unconventional method of Cross Site Request Forgery may be made exploitable by using Firefox versions 21 and below. The exploit requires that the target application be first vulnerable to HEAD request verb tampering, which is where a HEAD verb(also commonly known as 'method') is supplied in place of a GET or POST, and is successfully processed by the application. Once this is found, an XMLHttpRequest(commonly abbreviated to 'XHR') request can be sent from an off-domain location with the .open() method invoked and HEAD supplied as the verb.

The XMLHttpRequest Living Standard specifications can be found here and defines how XHR objects should be used. Although there are many rules, steps 3 and 4 of the .send() method serve particular interest to this implementation error:

.send(data);

3) If the request method is GET or HEAD, set data to null.

4) If data is null, do not include a request entity body and go to the next step.

Consider the following very basic and elementary Proof of Concept:

If you monitor your traffic or catch this in an intercepting proxy, you will see a request being made to https://www.whitehatsec.com with post data "foo=bar", even though the request verb is HEAD. According to step 3 above, 'data' should have been set to 'NULL'. This behavior seems to only occur in Firefox; The latest versions(as of this writing) of Internet Explorer, Chrome, Safari, and Opera are all successfully practicing proper .send() implementation.

I notified Mozilla of this behavior and a patch has been implemented into the v22 build. Until then Firefox 21 and those that refuse to ever update their browser will remain susceptible targets. It requires a bit of a "perfect storm" scenario, but nonetheless the second most widely used browser in the world should never ineptly contribute to CSRF.