/ 
Mojolicious-9.45
⭐ Starred 2674 / Mojo::BaseUtil
Security Advisories (2)
CVE-2024-58134 (2025-05-03)

Mojolicious versions from 0.999922 for Perl uses a hard coded string, or the application's class name, as an HMAC session cookie secret by default. These predictable default secrets can be exploited by an attacker 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.

CVE-2024-58135 (2025-05-03)

Mojolicious versions from 7.28 for Perl will generate weak HMAC session cookie secrets via "mojo generate app" by default When creating a default app skeleton 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.

NAME

Mojo::BaseUtil - Common utility functions used in Mojo::Base, re-exported in Mojo::Util

SYNOPSIS

use Mojo::BaseUtil qw(class_to_path monkey_patch);

my $path = class_to_path 'Foo::Bar';
monkey_patch 'MyApp', foo => sub { say 'Foo!' };

DESCRIPTION

Mojo::BaseUtil provides functions to both Mojo::Base and Mojo::Util, so that Mojo::Base does not have to load the rest of Mojo::Util, while preventing a circular dependency.

SEE ALSO

Mojolicious, Mojolicious::Guides, https://mojolicious.org.