Cross-Site Request Forgery (CSRF)

Last revision (mm/dd/yy): //

Overview
Cross-Site Request Forgery (CSRF) is an attack which forces an end user to execute unwanted actions on a web application in which he/she is currently authenticated. CSRF attacks specifically target state-changing requests, not theft of data, since the attacker has no way to see the response to the forged request. With a little help of social engineering (like sending a link via email/chat), an attacker may trick the users of a web application into executing actions of the attacker's choosing. If the victim is a normal user, a successful CSRF attack can force the user to perform state changing requests like transfering funds, changing their email address, etc. If the victim is an administrative account, CSRF can compromise the entire web application.

How to Review Code for CSRF Vulnerabilities
See the OWASP Code Review Guide article on how to Reviewing code for CSRF Vulnerabilities.

How to Test for CSRF Vulnerabilities
See the OWASP Testing Guide article on how to Test for CSRF Vulnerabilities.

How to Prevent CSRF Vulnerabilities
See the OWASP CSRF Prevention Cheat Sheet for prevention measures.

Listen to the OWASP Top Ten CSRF Podcast.

Most frameworks have built-in CSRF support such as Joomla, Spring, Struts, Ruby on Rails, .NET and others.

Use OWASP CSRF Guard to add CSRF protection to your Java applications. You can use CSRFProtector Project to protect your php applications or any project deployed using Apache Server. There is a .Net CSRF Guard at OWASP as well, but its old and doesn't look complete.

John Melton also has an excellent blog post describing how to use the native anti-CSRF functionality of the OWASP ESAPI.

Description
CSRF is an attack that tricks the victim into submitting a malicious request. It is malicious in the sense that it inherits the identity and privileges of the victim to perform an undesired function on the victim's behalf. For most sites, browser requests automatically include any credentials associated with the site, such as the user's session cookie, IP address, Windows domain credentials, etc. Therefore, if the user is currently authenticated to the site, the site will have no way to distinguish the forged request sent by the victim from a legitimate request sent by the victim.

CSRF attacks target functionality that causes a state change on the server, such as change the victim's e-mail address, home address, password, or purchase something. Forcing the victim to retrieve data doesn't benefit an attacker because the attacker doesn't receive the response, the victim does. As such, CSRF attacks target state-changing requests.

Sometimes, it is possible to store the CSRF attack on the vulnerable site itself. Such vulnerabilities are called Stored CSRF flaws. This can be accomplished by simply storing an IMG or IFRAME tag in a field that accepts HTML, or by a more complex cross-site scripting attack. If the attack can store a CSRF attack in the site, the severity of the attack is amplified. In particular, the likelihood is increased because the victim is more likely to view the page containing the attack than some random page on the Internet. The likelihood is also increased because the victim is sure to be authenticated to the site already.

Synonyms: CSRF attacks are also known by a number of other names, including XSRF, "Sea Surf", Session Riding, Cross-Site Reference Forgery, and Hostile Linking. Microsoft refers to this type of attack as a One-Click attack in their threat modeling process and many places in their online documentation.

Prevention measures that do NOT work

 * Using a secret cookie
 * Remember that all cookies, even the secret ones, will be submitted with every request. All authentication tokens will be submitted regardless of whether or not the end-user was tricked into submitting the request. Furthermore, session identifiers are simply used by the application container to associate the request with a specific session object. The session identifier does not verify that the end-user intended to submit the request.


 * Only accepting POST requests
 * Applications can be developed to only accept POST requests for the execution of business logic. The misconception is that since the attacker cannot construct a malicious POST request, a CSRF attack cannot be executed. Unfortunately, this logic is incorrect. There are numerous methods in which an attacker can trick a victim into submitting a forged POST request, such as a simple form hosted on the attacker's website comprised entirely of hidden fields. This form can be triggered automatically by JavaScript or can be triggered by the victim who thinks the form will do something else.

How does the attack work?
There are numerous ways in which an end-user can be tricked into loading information from or submitting information to a web application. In order to execute an attack, we must first understand how to generate a valid malicious request for our victim to execute. Let us consider the following example: Alice wishes to transfer $100 to Bob using the bank.com web application that is vulnerable to CSRF. Maria, an attacker, wants to trick Alice to send the money to her instead. The attack will comprise the following steps:


 * building an exploit URL or script,
 * tricking Alice into executing the action with Social Engineering

GET scenario
If the application was designed to primarily use GET requests to transfer parameters and execute actions, the money transfer operation might be reduced to a request like:

GET http://bank.com/transfer.do?acct=BOB&amount=100 HTTP/1.1

Maria now decides to exploit this web application vulnerability using Alice as her victim. Maria first constructs the following exploit URL which will transfer $100,000 from Alice's account to her account. She takes the original command URL and replaces the beneficiary name with herself, raising the transfer amount significantly at the same time:

http://bank.com/transfer.do?acct=MARIA&amount=100000

The Social Engineering part of the attack will trick Alice to load this URL when she's logged into the bank application. This is usually done with one of the following techniques:


 * sending an unsolicited email with HTML content
 * planting an exploit URL or script on pages that are likely to be visited by the victim while they are also doing online banking.

The exploit URL can be disguised either as an ordinary link, encouraging the victim to click it:

View my Pictures!

Or by a 0x0 fake image:



If this image tag were included in the email, Alice wouldn't see anything. However, the browser will still submit the request to bank.com without any visual indication that the transfer has taken place.

A real life example of CSRF attack on an application using GET was uTorrent exploit from 2008 that was used on a mass scale to download malware.

POST scenario
The only difference when POST requests are being used is how the attack is being executed by the victim. Let's assume the bank now uses POST and the vulnerable request looks like this:

POST http://bank.com/transfer.do HTTP/1.1 acct=BOB&amount=100

Such a request cannot be delivered using standard A or IMG tags, but can be delivered using a FORM tag:

   

This form will require the user to click on the submit button, but this can be also executed automatically using JavaScript:

 <form...

Other HTTP methods
Modern web application APIs are frequently using other HTTP methods such as PUT or DELETE. Let's assume the vulnerable bank uses PUT method that takes a JSON block as an argument:

PUT http://bank.com/transfer.do HTTP/1.1 {"acct":"BOB", "amount":100}

Such requests can be executed with JavaScript embedded into an exploit page:

function put { var x = new XMLHttpRequest; x.open("PUT"," http://bank.com/transfer.do ",true); x.setRequestHeader("Content-Type", "application/json"); x.send(JSON.stringify('{"acct":"BOB", "amount":100}')); } 

Fortunately, this request will not be executed by modern web browsers thanks to Same-Origin Policy restrictions. This restriction is enabled by default unless the target web site explicitly opens up Cross Origin Requests from the attacker's (or everyone's) origin by using CORS with the following header:

Access-Control-Allow-Origin: *

Related Attacks

 * Cross-site Scripting (XSS)
 * Cross Site History Manipulation (XSHM)

Related Controls

 * Add a per-request nonce to URL and all forms in addition to the standard session. This is also referred to as "form keys". Many frameworks (ex, Drupal.org 4.7.4+) either have or are starting to include this type of protection "built-in" to every form so the programmer does not need to code this protection manually.
 * Add a per-session nonce to all forms
 * Add a hash(session id, function name, server-side secret) to all forms
 * .NET - add session identifier to ViewState with MAC (Described in detail in: the CSRF Prevention Cheat Sheet)
 * Checking the referer header in the client's HTTP request can prevent CSRF attacks. By ensuring the HTTP request have come from the original site means that the attacks from other sites will not function.  It is very common to see referer header checks used on embedded network hardware due to memory limitations.  XSS can be used to bypass both referer and token based checks simultaneously.  For instance the Sammy Worm used an XHR to obtain the CSRF token to forge requests.
 * "Although CSRF is fundamentally a problem with the web application, not the user, users can help protect their accounts at poorly designed sites by logging off the site before visiting another, or clearing their browser's cookies at the end of each browser session." -http://en.wikipedia.org/wiki/Cross-site_request_forgery#_note-1
 * Tokenizing