Impact
If the CookieAuthenticator authentication is not encrypted it is vulnerable to authentication bypass, and potential CPU/memory exhaustion through forged tokens.
Patches
2.11.2, 3.3.7, 4.2.1 contain a fix for this issue. These releases introduce a new cookie format with backwards compatibility for existing token data. The compatibility for existing tokens can be disabled by setting legacyTokens = false when configuring a CookieAuthenticator.
Workarounds
Enable EncryptedCookieMiddleware with CookieAuth (or your cookie name).
Impact
If the
CookieAuthenticatorauthentication is not encrypted it is vulnerable to authentication bypass, and potential CPU/memory exhaustion through forged tokens.Patches
2.11.2, 3.3.7, 4.2.1 contain a fix for this issue. These releases introduce a new cookie format with backwards compatibility for existing token data. The compatibility for existing tokens can be disabled by setting
legacyTokens = falsewhen configuring aCookieAuthenticator.Workarounds
Enable
EncryptedCookieMiddlewarewithCookieAuth(or your cookie name).