/ 
Mojolicious-9.42
River stage four • 1019 direct dependents • 1130 total dependents
⭐ Starred 2674 GitHub stars
/ Mojo::Cache
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 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.

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

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.

NAME

Mojo::Cache - Naive in-memory cache

SYNOPSIS

use Mojo::Cache;

my $cache = Mojo::Cache->new(max_keys => 50);
$cache->set(foo => 'bar');
my $foo = $cache->get('foo');

DESCRIPTION

Mojo::Cache is a naive in-memory cache with size limits.

ATTRIBUTES

Mojo::Cache implements the following attributes.

max_keys

my $max = $cache->max_keys;
$cache  = $cache->max_keys(50);

Maximum number of cache keys, defaults to 100. Setting the value to 0 will disable caching.

METHODS

Mojo::Cache inherits all methods from Mojo::Base and implements the following new ones.

get

my $value = $cache->get('foo');

Get cached value.

set

$cache = $cache->set(foo => 'bar');

Set cached value.

SEE ALSO

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