Vulnerability in io.ratpack:ratpack-session (CVE-2021-29481)
Summary
Vulnerability in io.ratpack:ratpack-session (CVE-2021-29481). Confidential information can be exposed externally. Mitigation: upgrade to 1.9.0 or later.
Original description
The description as published by the source.
Ratpack is a toolkit for creating web applications. In versions prior to 1.9.0, the default configuration of client side sessions results in unencrypted, but signed, data being set as cookie values. This means that if something sensitive goes into the session, it could be read by something with access to the cookies. For this to be a vulnerability, some kind of sensitive data would need to be stored in the session and the session cookie would have to leak. For example, the cookies are not configured with httpOnly and an adjacent XSS vulnerability within the site allowed capture of the cookies. As of version 1.9.0, a securely randomly generated signing key is used. As a workaround, one may supply an encryption key, as per the documentation recommendation.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-29481 has been found in io.ratpack:ratpack-session.
Confidential information can be exposed externally.
What to do: upgrade io.ratpack:ratpack-session to 1.9.0 or later.
If unsure, ask your IT team or search "io.ratpack:ratpack-session CVE-2021-29481" on the vendor's site.
CVE-2021-29481 (io.ratpack:ratpack-session) — CWE-312
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.9.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-312) exists in io.ratpack:ratpack-session.
Check the vendor advisory for the affected versions of io.ratpack:ratpack-session.
Severity: ?. Confidential information can be exposed externally.
Update to 1.9.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで io.ratpack:ratpack-session を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade io.ratpack:ratpack-session to 1.9.0ステージング環境で 1.9.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com