# CVE-2022-23633: Exposure of sensitive information in Action Pack > Attackers can leak sensitive data from previous requests due to improper thread state resetting in Action Pack. - **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 11 Feb 2022 - **Updated:** 3 Aug 2024 - **Also known as:** DEBIAN-CVE-2022-23633, GHSA-wh98-p28r-vrc9, OESA-2024-1762, OESA-2024-1763, OESA-2024-1764, OESA-2024-1777, OESA-2024-1778, OESA-2024-1779, OESA-2024-1810, UBUNTU-CVE-2022-23633, openSUSE-SU-2024:11869-1, openSUSE-SU-2024:11899-1, openSUSE-SU-2024:12878-1 ## What is CVE-2022-23633? CVE-2022-23633 is a high-severity vulnerability in Debian Debian Linux, published on 11 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-212 (Improper Removal of Sensitive Information Before Storage or Transfer), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2022-23633? 8 open source packages ship an affected version, including actionpack. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `actionpack` | RubyGems | From 5.0.0.0 | 5.2.6.2 | | `actionpack` | RubyGems | From 5.0.0.0 | 5.2.6.2 | | `actionpack` | RubyGems | From 6.0.0.0 | 6.0.4.6 | | `actionpack` | RubyGems | From 6.0.0.0 | 6.0.4.6 | | `actionpack` | RubyGems | From 6.1.0.0 | 6.1.4.6 | | `actionpack` | RubyGems | From 6.1.0.0 | 6.1.4.6 | | `actionpack` | RubyGems | From 7.0.0.0 | 7.0.2.2 | | `actionpack` | RubyGems | From 7.0.0.0 | 7.0.2.2 | | `ruby3.2-rubygem-actionpack-7.0` | openSUSE:Tumbleweed | All versions | 7.0.4.3-1.1 | | `rubygem-actionpack-6.0` | openSUSE:Tumbleweed | All versions | 6.0.4.6-1.1 | | `rubygem-actionpack-7.0` | openSUSE:Tumbleweed | All versions | 7.0.2.2-1.1 | Products: Debian Debian Linux, Rubyonrails Rails. ## How do I fix CVE-2022-23633? Upgrade actionpack to a fixed version for your release line: 5.2.6.2, 6.0.4.6, 6.1.4.6 or 7.0.2.2. ## Is CVE-2022-23633 being exploited? There is no known exploitation of CVE-2022-23633 in the wild and no public exploit code. ## Other vulnerabilities in Debian Debian Linux - [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild) - [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild) - [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild) - [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild) - [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-23633 and fix it if it is affected. What it is: CVE-2022-23633 is a high-severity vulnerability in Debian Debian Linux, published on 11 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2022-23633 in the wild and no public exploit code. Affected packages and fixed versions: - actionpack (RubyGems): affected from 5.0.0.0; fixed in 5.2.6.2 - actionpack (RubyGems): affected from 5.0.0.0; fixed in 5.2.6.2 - actionpack (RubyGems): affected from 6.0.0.0; fixed in 6.0.4.6 - actionpack (RubyGems): affected from 6.0.0.0; fixed in 6.0.4.6 - actionpack (RubyGems): affected from 6.1.0.0; fixed in 6.1.4.6 - actionpack (RubyGems): affected from 6.1.0.0; fixed in 6.1.4.6 - actionpack (RubyGems): affected from 7.0.0.0; fixed in 7.0.2.2 - actionpack (RubyGems): affected from 7.0.0.0; fixed in 7.0.2.2 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2022-23633/ (Markdown: https://insights.sbomify.com/CVE-2022-23633/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-23633 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-23633 - OSV: https://osv.dev/vulnerability/CVE-2022-23633 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-23633/ Summaries are generated and may contain mistakes; the official description above is the record.