Impact
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.
Vulnerability Location
|
private String secretToken = Long.toString(System.currentTimeMillis() / 10000); |
Patches
As of Ratpack 1.9.0 the default value is a securely randomly generated value, generated at application startup time.
Workarounds
Supply an alternative signing key, as per the documentation's recommendation.
JLLeitschuh Analyst
Impact
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.
Vulnerability Location
ratpack/ratpack-session/src/main/java/ratpack/session/clientside/ClientSideSessionConfig.java
Line 29 in 29434f7
Patches
As of Ratpack 1.9.0 the default value is a securely randomly generated value, generated at application startup time.
Workarounds
Supply an alternative signing key, as per the documentation's recommendation.