mirror of
https://github.com/samsonjs/rack-attack.git
synced 2026-03-25 09:25:49 +00:00
76c2e31430
The issue
---
When using rack-attack with a rails app, developers expect the request
path to be normalized. In particular, trailing slashes are stripped so
a request path "/login/" becomes "/login" by the time you're in
ActionController.
Since Rack::Attack runs before ActionDispatch, the request path is not
yet normalized. This can cause throttles and blacklists to not work as
expected.
E.g., a throttle:
throttle('logins', ...) {|req| req.path == "/login" }
would not match a request to '/login/', though Rails would route
'/login/' to the same '/login' action.
The solution
---
This patch looks if ActionDispatch's request normalization is loaded,
and if so, uses it to normalize the path before processing throttles,
blacklists, etc.
If it's not loaded, the request path is not modified.
Credit
---
Thanks to Andres Riancho at Include Security for reporting this issue.
27 lines
924 B
Ruby
27 lines
924 B
Ruby
class Rack::Attack
|
|
|
|
# When using Rack::Attack with a Rails app, developers expect the request path
|
|
# to be normalized. In particular, trailing slashes are stripped.
|
|
# (See http://git.io/v0rrR for implementation.)
|
|
#
|
|
# Look for an ActionDispatch utility class that Rails folks would expect
|
|
# to normalize request paths. If unavailable, use a fallback class that
|
|
# doesn't normalize the path (as a non-Rails rack app developer expects).
|
|
|
|
module FallbackPathNormalizer
|
|
def self.normalize_path(path)
|
|
path
|
|
end
|
|
end
|
|
|
|
PathNormalizer = if defined?(::ActionDispatch::Journey::Router::Utils)
|
|
# For Rails 4+ apps
|
|
::ActionDispatch::Journey::Router::Utils
|
|
elsif defined?(::Journey::Router::Utils)
|
|
# for Rails 3.2
|
|
::Journey::Router::Utils
|
|
else
|
|
FallbackPathNormalizer
|
|
end
|
|
|
|
end
|