New Reebok ZigKick Tactical line re-engineers el... » St. Louis, MO: Warson Brands, official licensee of Reebok tactical footwear, introduces the new Reeb... Security Council extends UN mission in South Sudan... » A wide view of the Security Council in session. UN Photo/Devra Berkowitz (file) Vigilance can ... Fire training in the build up to be... » Lee Coates, Wrightstyle's technical director, looks at fire training in the build up to Christmas... Running For Their Lives? Reflections On The Curren... » The present mass movement of humans has been more widely described as that by “migrants” than that b... BSIA welcomes revision of British Standard BS7958 » James Kelly, CEO, BSIA The British Security Industry Association (BSIA) has welcomed the rev... ASIS International announces three Board certifica... » Alexandria, Va. (Oct. 9, 2015) – ASIS International (ASIS), today announced that the American Counci... NATO Secretary General strongly condemns terrorist... » Jens Stoltenberg I strongly condemn the terrorist attack in the centre of Ankara that killed and ... Securonix joins the Intelligence and National Secu... » LOS ANGELES: Securonix has announced that it is proud to join The Intelligence and National Security... Digital Guardian acquires Code Green Networks » London, United Kingdom: Digital Guardian has acquired Code Green Networks, a provider of Data Loss P... QuintessenceLabs selected as a SINET top 16 emergi... » SAN JOSE, Calif: Vigilance can report that QuintessenceLabs is a winner in the annual SINET 16 Innov...


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.


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:


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 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.