How Attackers Exploit People to Circumvent Cyber... » LONDON, UK: Proofpoint, Inc. has released the results of its annual study that details the ways atta... Check Point and FireEye announce new partnership t... » San Francisco, CA: Check Point Software Technologies Ltd and FireEye have announced a partnership to... gateprotect offers companies high security encod... » Hamburg: gateprotect GmbH, a German IT security specialist and subsidiary of the Rohde & Schwarz cor... BeyondTrust Solution for Privileged Account Manage... » PHOENIX: BeyondTrust has announced that the company’s PowerBroker for Windows has been selected as a... The end of Goodluck and the beginning of the Buhar... » Against all odds, the 2015 Presidential election initially billed for February 14, but rescheduled t... Thales announces integration of nShield with Citr... » San Francisco, CA and Plantation, Fla.:  Thales has announce the integration of its nShield hardware... Thales wins with customer Qube Cinema 2015 InfoSec... » Thales has won the silver award for Best Deployment and Case Study in InfoSecurity Products Guide Gl... Wick Hill now shipping Barracuda Mobile Device Man... » Woking, Surrey: Wick Hill is now shipping Barracuda’s Mobile Device Manager (MDM) solution with supp... Databarracks recognised in Gartner's Magic Quadran... » London: Databarracks has been recognised in Gartner’s Magic Quadrant for Disaster Recovery as a Serv... Campaigners draw up battle lines to boost power... » Gate safety campaigners are once again mounting a high profile drive to raise awareness of the safet...

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.