request_forgery_protection.rb 5.1 KB
Newer Older
J
Jeremy Kemper 已提交
1 2
require 'active_support/core_ext/class/attribute'

3
module ActionController #:nodoc:
4 5
  class InvalidAuthenticityToken < ActionControllerError #:nodoc:
  end
6 7

  module RequestForgeryProtection
8
    extend ActiveSupport::Concern
9

10
    include AbstractController::Helpers
11 12

    included do
13 14 15
      # Sets the token parameter name for RequestForgery. Calling +protect_from_forgery+
      # sets it to <tt>:authenticity_token</tt> by default.
      cattr_accessor :request_forgery_protection_token
16

17
      # Controls whether request forgergy protection is turned on or not. Turned off by default only in test mode.
J
Jeremy Kemper 已提交
18
      class_attribute :allow_forgery_protection
19
      self.allow_forgery_protection = true
20 21 22

      helper_method :form_authenticity_token
      helper_method :protect_against_forgery?
23
    end
24 25 26

    # Protecting controller actions from CSRF attacks by ensuring that all forms are coming from the current
    # web application, not a forged link from another site, is done by embedding a token based on a random
Y
Yehuda Katz 已提交
27
    # string stored in the session (which an attacker wouldn't know) in all forms and Ajax requests generated
28 29 30
    # by Rails and then verifying the authenticity of that token in the controller.  Only HTML/JavaScript
    # requests are checked, so this will not protect your XML API (presumably you'll have a different
    # authentication scheme there anyway).  Also, GET requests are not protected as these should be
Y
Yehuda Katz 已提交
31
    # idempotent anyway.
32 33
    #
    # This is turned on with the <tt>protect_from_forgery</tt> method, which will check the token and raise an
34
    # ActionController::InvalidAuthenticityToken if it doesn't match what was expected. You can customize the
Y
Yehuda Katz 已提交
35 36
    # error message in production by editing public/422.html.  A call to this method in ApplicationController is
    # generated by default in post-Rails 2.0 applications.
37
    #
38 39 40
    # The token parameter is named <tt>authenticity_token</tt> by default. If you are generating an HTML form
    # manually (without the use of Rails' <tt>form_for</tt>, <tt>form_tag</tt> or other helpers), you have to
    # include a hidden field named like that and set its value to what is returned by
Y
Yehuda Katz 已提交
41
    # <tt>form_authenticity_token</tt>.
42
    #
43
    # Request forgery protection is disabled by default in test environment. If you are upgrading from Rails
Y
Yehuda Katz 已提交
44
    # 1.x, add this to config/environments/test.rb:
45 46 47
    #
    #   # Disable request forgery protection in test environment
    #   config.action_controller.allow_forgery_protection = false
48
    #
49 50 51 52 53 54 55 56
    # == Learn more about CSRF (Cross-Site Request Forgery) attacks
    #
    # Here are some resources:
    # * http://isc.sans.org/diary.html?storyid=1750
    # * http://en.wikipedia.org/wiki/Cross-site_request_forgery
    #
    # Keep in mind, this is NOT a silver-bullet, plug 'n' play, warm security blanket for your rails application.
    # There are a few guidelines you should follow:
57
    #
58 59 60
    # * Keep your GET requests safe and idempotent.  More reading material:
    #   * http://www.xml.com/pub/a/2002/04/24/deviant.html
    #   * http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.1.1
61
    #   * Make sure the session cookies that Rails creates are non-persistent.  Check in Firefox and look
Y
Yehuda Katz 已提交
62
    #     for "Expires: at end of session"
63
    #
64
    module ClassMethods
65
      # Turn on request forgery protection. Bear in mind that only non-GET, HTML/JavaScript requests are checked.
66
      #
D
David Heinemeier Hansson 已提交
67 68 69 70 71
      # Example:
      #
      #   class FooController < ApplicationController
      #     protect_from_forgery :except => :index
      #
72 73
      #     # you can disable csrf protection on controller-by-controller basis:
      #     skip_before_filter :verify_authenticity_token
D
David Heinemeier Hansson 已提交
74 75 76 77
      #   end
      #
      # Valid Options:
      #
P
Pratik Naik 已提交
78
      # * <tt>:only/:except</tt> - Passed to the <tt>before_filter</tt> call.  Set which actions are verified.
79 80
      def protect_from_forgery(options = {})
        self.request_forgery_protection_token ||= :authenticity_token
Y
Yehuda Katz 已提交
81
        before_filter :verify_authenticity_token, options
82 83 84 85 86
      end
    end

    protected
      # The actual before_filter that is used.  Modify this to change how you handle unverified requests.
87
      def verify_authenticity_token
88
        verified_request? || raise(ActionController::InvalidAuthenticityToken)
89
      end
Y
Yehuda Katz 已提交
90

91 92
      # Returns true or false if a request is verified.  Checks:
      #
93
      # * is the format restricted?  By default, only HTML requests are checked.
94
      # * is it a GET request?  Gets should be safe and idempotent
95
      # * Does the form_authenticity_token match the given token value from the params?
96
      def verified_request?
97
        !protect_against_forgery? || request.forgery_whitelisted? ||
98
          form_authenticity_token == params[request_forgery_protection_token]
99
      end
Y
Yehuda Katz 已提交
100

P
Pratik Naik 已提交
101
      # Sets the token value for the current session.
102
      def form_authenticity_token
103
        session[:_csrf_token] ||= ActiveSupport::SecureRandom.base64(32)
104
      end
105

106 107 108 109 110
      # The form's authenticity parameter. Override to provide your own.
      def form_authenticity_param
        params[request_forgery_protection_token]
      end

111
      def protect_against_forgery?
J
Jeremy Kemper 已提交
112
        self.class.allow_forgery_protection
113
      end
114
  end
115
end