actionpack
Affected
- introduced
5.0.0.0, fixed5.2.6.2(ecosystem)
Fixed versions
5.2.6.2
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2022-23633
Exposure of information in Action Pack
Impact
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.
Patches
This has been fixed in Rails 7.0.2.2, 6.1.4.6, 6.0.4.6, and 5.2.6.2.
Workarounds
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
endHigh Basis: The source's own band: HIGH
5.0.0.0, fixed 5.2.6.2 (ecosystem)5.2.6.2
The export has no generic command for this ecosystem.
6.0.0.0, fixed 6.0.4.6 (ecosystem)6.0.4.6
The export has no generic command for this ecosystem.
6.1.0.0, fixed 6.1.4.6 (ecosystem)6.1.4.6
The export has no generic command for this ecosystem.
7.0.0.0, fixed 7.0.2.2 (ecosystem)7.0.2.2
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0