Exposure of sensitive information in Action Pack
rails
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| actionpack RubyGems |
|
|
rails
| Product | Affected | Fixed in |
|---|---|---|
| actionpack RubyGems |
|
|
Action Pack is a framework for handling and responding to web requests. Under certain circumstances response bodies will not be closed. 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.This has been fixed in Rails 7.0.2.1, 6.1.4.5, 6.0.4.5, and 5.2.6.1. Upgrading is highly recommended, but to work around this problem a middleware described in GHSA-wh98-p28r-vrc9 can be used.
From the CVE record · GitHub_M
Under certain circumstances, an Action Pack response body is not closed, leaving ActionDispatch::Executor unable to reset thread-local state. Data can then leak to subsequent web requests; the input does not specify whether authentication or user interaction is required.
Teams running the RubyGems actionpack package should check versions >=5.0.0.0 <5.2.6.2, >=6.0.0.0 <6.0.4.6, >=6.1.0.0 <6.1.4.6, or >=7.0.0.0 <7.0.2.2.