What Is a CSRF Attack and How to Prevent ItVishnu Yash Tripathi
Cross-site Request Forgery (CSRF/XSRF), also known as sea surf or session riding, refers to an attack against authenticated web applications using cookies. The hacker is able to trick the victim into making a request that the victim did not intend to make. Therefore, the hacker abuses the trust that a web application has for the victim’s browser. While Cross-site Request Forgery (CSRF) attacks do not provide anything to an attacker with the response returned from the server, a clever attacker could cause a fair amount of damage, especially when paired with well-crafted social engineering attacks on administrative users.
XSRF is a type of unwanted confused attacks, which validates the authentication and authorization of the victim when a fake request is being sent to the web server. Therefore, a Cross Site Request Forgery vulnerability that affects highly privileged users, such as administrators, could result in a full application compromise. During a successful XSRF (Cross-site Request Forgery attack) the victim’s web browser is tricked by a malicious website into unwanted action – it sends HTTP requests to the web application as intended by the attacker. Generally, such a request would involve submitting forms present on the web application to alter some data.
Upon sending an HTTP request the victim’s web browser will include the cookie header. Cookies are typically used to store a user’s session identifier so that the user does not have to enter their login credentials for each request, which would obviously be impractical. If the users authenticated session is stored in a browser session cookie that is still valid (a browser window/tab does not necessarily need to be open), and if the application is vulnerable to Cross-site Request Forgery (CSRF), then the attacker can validates CSRF to launch any desired malicious requests against the website and the server-side code is unable to distinguish whether these are legitimate requests.
CSRF attacks may, for example, be used to compromise online banking by forcing the victim to make an operation involving their bank account. CSRF can also evaluate as Cross-site Scripting (XSS).Therefore, CSRF should be treated as a serious web application security issue, even if it is not currently included in the OWASP Top 10.
Cross-site Request Forgery in GET Requests
The below simple example of how Cross-site Request Forgery (CSRF) can be abused in GET requests through the use of the <img>tag.
The above URL is a CSRF attack using an HTTP GET request. If the attacker visits a web page controlled by the hacker with the following payload, the browser will send a request containing the web cookie to the attacker-crafted URL.
Cross-site Request Forgery in POST Requests
The following is a simple example of how CSRF can be abused using POST requests through the use of an <iframe>tag. This code would be loaded in an iframe which is made not visible to the victim.
<iframe src=”http://attacker.com/csrfAttack” style=”width:0;height:0;border:0;border:none;”></iframe>
iframe HTML contents
<form id=”csrf” action=”http://example.com/changePassword.php” method=”POST”>
<input name=”newPassword” value=”attackerPassword” />
Generally there are two primary approaches to protect Cross-site Request Forgery (CSRF) –
1- synchronizing the cookie with an anti-CSRF token that has already been provided to the browser.
2- Preventing the browser from sending cookies to the web application in the first place.
The recommended and the most used prevention technique for Cross-site Request Forgery (CSRF) attacks is called as an anti-CSRF token, sometimes referred to as a synchronizer token or just simply a CSRF token. When any type user submits a form or makes some other authenticated request that requires a cookie, then any random token should be included in the request. The web application will then validate the existence and correctness of this token before processing the request. If the token is missing or invalid the request can be rejected.
It is highly recommended that you are using an existing, well tested and reliable anti-CSRF library. Depending on your own language and framework of choice, there are several high-quality open source libraries that are ready-to-use. The characteristics of a well developed anti-CSRF system involve into the following attributes:
- The anti-CSRF token should be always unique for each user session
- The session should automatically expire after a fixed amount of time
- The anti-CSRF token should be a cryptographically random value of sufficient length.
- The anti-CSRF token should be cryptographically secure, that is, generated by a strong pseudo-random number generator algorithm
- The anti-CSRF token can be added as a hidden field for forms or within request URLs.
- The server should reject the request action if the anti-CSRF token fails validation.
SameSite Cookies: The SameSite cookie attribute is a new attribute that can be set on browser cookies to instruct the browser to disable third-party usage for unique cookies. The SameSite attribute is set by the web server when setting the cookie and requests the browser to only send the cookie in a first-party context. Therefore, the request has to initiate from the same origin – requests made by third-party sites will not include the SameSite cookie. This effectively deletes Cross-site Request Forgery attacks without the use of synchronizer tokens. Unfortunately, this method of CSRF protection is not yet more effective in all web browsers but many more browsers start to use it.
How to Protect Cross-site Request Forgery (CSRF) – Generic Tips
Cross-site Request Forgery (CSRF) vulnerabilities are very harmful partly because preventing them is not that easy. There are different methods that you can use to avoid them but not all are effective in all scenarios. In addition to two different methods that are considered the most effective, there are fixed general strategic principles that you should follow to keep your web application safe.