Vulnerability in io.ratpack:ratpack-core (CVE-2021-29479)
Summary
Vulnerability in io.ratpack:ratpack-core (CVE-2021-29479). Risk of unauthorized operations or information disclosure. Exploitable via PublicAddress. 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, a user supplied X-Forwarded-Host header can be used to perform cache poisoning of a cache fronting a Ratpack server if the cache key does not include the X-Forwarded-Host header as a cache key. Users are only vulnerable if they do not configure a custom PublicAddress instance. For versions prior to 1.9.0, by default, Ratpack utilizes an inferring version of PublicAddress which is vulnerable. This can be used to perform redirect cache poisoning where an attacker can force a cached redirect to redirect to their site instead of the intended redirect location. The vulnerability was patched in Ratpack 1.9.0. As a workaround, ensure that ServerConfigBuilder::publicAddress correctly configures the server in production.
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-29479 has been found in io.ratpack:ratpack-core.
Attackers can target a specific entry point like PublicAddress over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade io.ratpack:ratpack-core to 1.9.0 or later.
If unsure, ask your IT team or search "io.ratpack:ratpack-core CVE-2021-29479" on the vendor's site.
CVE-2021-29479 (io.ratpack:ratpack-core) — CWE-807
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: PublicAddress
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-807) exists in io.ratpack:ratpack-core. Attackers reach the vulnerable code path via PublicAddress without authentication.
Check the vendor advisory for the affected versions of io.ratpack:ratpack-core. Attack surface: PublicAddress.
Severity: ?. Risk of unauthorized operations or information disclosure.
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-core を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade io.ratpack:ratpack-core 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
- report portswigger.net