Exposure of sensitive information in Action Pack
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 7.0.2.1, 6.1.4.5, 6.0.4.5, 5.2.6.1, 5.2.6.2, and 3 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- rails rails
From 7.0.0.0 · fixed in 7.0.2.1; From 6.1.0.0 · fixed in 6.1.4.5; From 6.0.0.0 · fixed in 6.0.4.5; From 5.0.0 · fixed in 5.2.6.1
- actionpackRubyGems
From 5.0.0.0 · fixed in 5.2.6.2
- actionpackRubyGems
From 6.0.0.0 · fixed in 6.0.4.6
- actionpackRubyGems
From 6.1.0.0 · fixed in 6.1.4.6
- actionpackRubyGems
From 7.0.0.0 · fixed in 7.0.2.2