Categories
CVE-2021-29480

Vulnerability in io.ratpack:ratpack-session (CVE-2021-29480)

Summary

Vulnerability in io.ratpack:ratpack-session (CVE-2021-29480). Risk of unauthorized operations or information disclosure. 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 client side session module uses the application startup time as the signing key by default. This means that if an attacker can determine this time, and if encryption is not also used (which is recommended, but is not on by default), the session data could be tampered with by someone with the ability to write cookies. The default configuration is unsuitable for production use as an application restart renders all sessions invalid and is not multi-host compatible, but its use is not actively prevented. As of Ratpack 1.9.0, the default value is a securely randomly generated value, generated at application startup time. As a workaround, supply an alternative signing key, as per the documentation's 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-29480 has been found in io.ratpack:ratpack-session.
Risk of unauthorized operations or information disclosure.
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-29480" on the vendor's site.

CVE-2021-29480 (io.ratpack:ratpack-session) — CWE-330
Attack vector: remote (network-reachable) / 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.

❓ What is the problem

A vulnerability (CWE-330) exists in io.ratpack:ratpack-session.

📍 Affected scope

Check the vendor advisory for the affected versions of io.ratpack:ratpack-session.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.9.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

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

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで io.ratpack:ratpack-session を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch
    Upgrade io.ratpack:ratpack-session to 1.9.0

    ステージング環境で 1.9.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Maven io.ratpack:ratpack-session
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.9.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details