CSRF protection weakened or disabled¶
ID: rb/csrf-protection-disabled Kind: problem Severity: warning Precision: high Tags: - security - external/cwe/cwe-352 Query suites: - ruby-code-scanning.qls - ruby-security-extended.qls - ruby-security-and-quality.qls
Cross-site request forgery (CSRF) is a type of vulnerability in which an attacker is able to force a user to carry out an action that the user did not intend.
The attacker tricks an authenticated user into submitting a request to the web application. Typically this request will result in a state change on the server, such as changing the user’s password. The request can be initiated when the user visits a site controlled by the attacker. If the web application relies only on cookies for authentication, or on other credentials that are automatically included in the request, then this request will appear as legitimate to the server.
A common countermeasure for CSRF is to generate a unique token to be included in the HTML sent from the server to a user. This token can be used as a hidden field to be sent back with requests to the server, where the server can then check that the token is valid and associated with the relevant user session.
In many web frameworks, CSRF protection is enabled by default. In these cases, using the default configuration is sufficient to guard against most CSRF attacks.
The following example shows a case where CSRF protection is disabled by skipping token verification.
class UsersController < ApplicationController skip_before_action :verify_authenticity_token end
Verification can be re-enabled by removing the call to
Care should be taken when using the Rails
protect_from_forgery method to prevent CSRF. The default behaviour of this method is to null the session when an invalid CSRF token is provided. This may not be sufficient to avoid a CSRF vulnerability - for example if parts of the session are memoized. Calling
protect_from_forgery with: :exception can help to avoid this by raising an exception on an invalid CSRF token instead.