Security readout for executives and security teams
Plain-English summary
Ratpack applications before 1.9.0 can be exposed to remote code execution if they use Ratpack's session mechanism. The issue is unsafe Java deserialization in session storage. Applications that do not use Ratpack sessions are not vulnerable according to the source bundle.
Executive priority
Treat as urgent for any Ratpack application using sessions, especially internet-facing services. RCE can support full application compromise. The fastest business decision is to identify Ratpack usage, confirm session exposure, and upgrade or apply the documented allow-list mitigation.
Technical view
CVE-2021-29485 is CWE-502 in Ratpack session storage. A malicious Java deserialization gadget chain can lead to RCE against vulnerable session handling. The CVSS 3.1 score is 9.9: network reachable, low complexity, low privileges required, no user interaction, and high impact.
Likely exposure
Exposure is likely limited to Ratpack versions before 1.9.0 where the application uses Ratpack's session mechanism. Risk rises where attackers can influence or write session data storage. Ratpack applications without that session mechanism are stated as not vulnerable.
Exploitation context
The bundle does not show CISA KEV listing or other evidence of active exploitation. The vendor advisory describes a malicious attacker achieving RCE through crafted Java deserialization against the session store, with CVSS indicating low privileges are required.
Researcher notes
Prioritize dependency discovery and runtime confirmation of Ratpack session usage. Do not assume all Ratpack applications are vulnerable. The key validation point is whether vulnerable versions deserialize attacker-influenced session data without the allow-list protection introduced in 1.9.0.
Mitigation direction
- Upgrade Ratpack to version 1.9.0 or later.
- Enable and use Ratpack 1.9.0's strict allow-list mechanism.
- For older versions, restrict attacker ability to write session data.
- Consider backporting allow-list behavior with an alternative SessionSerializer.
- Check current vendor guidance before relying on compensating controls.
Validation and detection
- Inventory applications using io.ratpack:ratpack-core below 1.9.0.
- Confirm whether each application uses Ratpack's session mechanism.
- Review whether untrusted users can influence or write session data.
- Verify the strict allow-list mechanism is enabled after upgrade.
- For backports, review the SessionSerializer for explicit allowed classes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-29485 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.9CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/ratpack/ratpack/security/advisories/GHSA-hc33-32vw-rpp9CVE reference · x_refsource_CONFIRM
- https://mvnrepository.com/artifact/io.ratpack/ratpack-coreCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.