| Package | Affected versions | Patched versions |
|---|---|---|
| actionpack | ≥ 5.0.0.0, < 5.2.6.2≥ 6.0.0.0, < 6.0.4.6≥ 6.1.0.0, < 6.1.4.6≥ 7.0.0.0, < 7.0.2.2 | 5.2.6.26.0.4.66.1.4.67.0.2.2 |
| rails | ≥ 5.0.0, < 5.2.6.2≥ 6.0.0, < 6.0.4.6≥ 6.1.0, < 6.1.4.6≥ 7.0.0, < 7.0.2.2 | 5.2.6.26.0.4.66.1.4.67.0.2.2 |
Under certain circumstances response bodies will not be closed, for example a bug in a webserver or a bug in a Rack middleware. In the event a response is not notified of a close, ActionDispatch::Executor will not know to reset thread local state for the next request. This can lead to data being leaked to subsequent requests, especially when interacting with ActiveSupport::CurrentAttributes.
Upgrading to the FIXED versions of Rails will ensure mitigation of this issue even in the context of a buggy webserver or middleware implementation.
This has been fixed in Rails 7.0.2.2, 6.1.4.6, 6.0.4.6, and 5.2.6.2.
Upgrading is highly recommended, but to work around this problem the following middleware can be used:
class GuardedExecutor < ActionDispatch::Executor
def call(env)
ensure_completed!
super
end
private
def ensure_completed!
@executor.new.complete! if @executor.active?
end
end
# Ensure the guard is inserted before ActionDispatch::Executor
Rails.application.configure do
config.middleware.swap ActionDispatch::Executor, GuardedExecutor, executor
end
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free