Mojolicious versions from 0.999922 for Perl uses a hard coded string, or the application's class name, as a HMAC session secret by default. These predictable default secrets can be exploited to forge session cookies. An attacker who knows or guesses the secret could compute valid HMAC signatures for the session cookie, allowing them to tamper with or hijack another user's session.

• https://github.com/hashcat/hashcat/pull/4090
• https://github.com/mojolicious/mojo/pull/1791
• https://github.com/mojolicious/mojo/pull/2200
• https://medium.com/securing/baking-mojolicious-cookies-revisited-a-case-study-of-solving-security-problems-through-security-by-13da7c225802
• https://metacpan.org/release/SRI/Mojolicious-9.39/source/lib/Mojolicious.pm#L51
• https://www.synacktiv.com/publications/baking-mojolicious-cookies
• https://www.cve.org/CVERecord?id=CVE-2024-58134

Mojolicious versions from 7.28 for Perl may generate weak HMAC session secrets. When creating a default app with the "mojo generate app" tool, a weak secret is written to the application's configuration file using the insecure rand() function, and used for authenticating and protecting the integrity of the application's sessions. This may allow an attacker to brute force the application's session keys.

• https://github.com/hashcat/hashcat/pull/4090
• https://github.com/mojolicious/mojo/pull/2200
• https://metacpan.org/release/SRI/Mojolicious-7.28/source/lib/Mojolicious/Command/generate/app.pm#L220
• https://metacpan.org/release/SRI/Mojolicious-9.38/source/lib/Mojolicious/Command/Author/generate/app.pm#L202
• https://metacpan.org/release/SRI/Mojolicious-9.39/source/lib/Mojo/Util.pm#L181
• https://perldoc.perl.org/functions/rand
• https://security.metacpan.org/docs/guides/random-data-for-security.html