Description
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.
Remediation
References
https://github.com/ratpack/ratpack/blob/29434f7ac6fd4b36a4495429b70f4c8163100332/ratpack-session/src/main/java/ratpack/session/clientside/ClientSideSessionConfig.java#L29
https://github.com/ratpack/ratpack/security/advisories/GHSA-2cc5-23r7-vc4v
Related Vulnerabilities
CVE-2017-16104 Vulnerability in npm package citypredict.whauwiller
CVE-2023-44487 Vulnerability in maven package io.helidon.http:helidon-http-http2
CVE-2022-0613 Vulnerability in npm package urijs
CVE-2015-8861 Vulnerability in maven package org.webjars.bower:handlebars
CVE-2012-5887 Vulnerability in maven package org.apache.tomcat.embed:tomcat-embed-core