Huawei and Commvault jointly launch the Hybrid C... » Huawei and Commvault have released their Hybrid Cloud Backup Solution at CeBIT 2017, currently takin... MOBOTIX brings innovation and partnerships to ISC ... » During ISC West from the 5th to 7th of April at Sands Expo in Las Vegas, NV, MOBOTIX (stand 16065), ... ST. MICHAEL'S OPENS DOORS WITH HELP FROM ERA » David Stapleton and Era’s Tania Tams with Mrs. Grundy and pupils at St Michael’s First School Vig... 17% growth ensures Nationwide Platforms remains wo... » Nationwide Platforms has once again retained its position as the world’s largest IPAF provider after... Le Pen Seeks Anti-terrorism Operations in Chad...B... » "Well, Marine Le Pen may be able to save France from abroad. But hold on for a minute, do you really... Synectics to showcase urban transport surveillance... » David AindowUrban transport networks are in danger of data overload. Guarding against emerging secur... TomTom Telematics collaborates with SOTI » TomTom Telematics has announced a collaboration with SOTI that will see the company’s popular flag... Dimension Data launches support and managed servic... » London, United Kingdom: Dimension Data has extended its current offering with Cisco Meraki. This inc... LOCKEN ANNOUNCES STRATEGIC COLLABORATION WITH ISEO » Leading developers of cable free access control, LOCKEN and ISEO Group, an Italian based designer,... Sopra Steria finds UK citizens want more secu... » London: Sopra Steria has revealed that UK citizens are keener than ever to use digital public servic...

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.