Security Advisories (10)
CPANSA-Mojolicious-2022-03 (2022-12-10)

Mojo::DOM did not correctly parse <script> tags.

CPANSA-Mojolicious-2021-02 (2021-06-01)

Small sessions could be used as part of a brute-force attack to decode the session secret.

CVE-2021-47208 (2021-03-16)

A bug in format detection can potentially be exploited for a DoS attack.

CVE-2018-25100 (2018-02-13)

Mojo::UserAgent::CookieJar leaks old cookies because of the missing host_only flag on empty domain.

CPANSA-Mojolicious-2015-01 (2015-02-02)

Directory traversal on Windows

CPANSA-Mojolicious-2018-03 (2018-05-19)

Mojo::UserAgent was not checking peer SSL certificates by default.

CVE-2020-36829 (2020-11-10)

Mojo::Util secure_compare can leak the string length. By immediately returning when the two strings are not the same length, the function allows an attacker to guess the length of the secret string using timing attacks.

CPANSA-Mojolicious-2018-02 (2018-05-11)

GET requests with embedded backslashes can be used to access local files on Windows hosts

CPANSA-Mojolicious-2014-01 (2014-10-07)

Context sensitivity of method param could lead to parameter injection attacks.

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.

NAME

Mojo::Asset::Memory - In-memory storage for HTTP content

SYNOPSIS

use Mojo::Asset::Memory;

my $mem = Mojo::Asset::Memory->new;
$mem->add_chunk('foo bar baz');
say $mem->slurp;

DESCRIPTION

Mojo::Asset::Memory is an in-memory storage backend for HTTP content.

EVENTS

Mojo::Asset::Memory inherits all events from Mojo::Asset and can emit the following new ones.

upgrade

$mem->on(upgrade => sub {
  my ($mem, $file) = @_;
  ...
});

Emitted when asset gets upgraded to a Mojo::Asset::File object.

$mem->on(upgrade => sub {
  my ($mem, $file) = @_;
  $file->tmpdir('/tmp');
});

ATTRIBUTES

Mojo::Asset::Memory inherits all attributes from Mojo::Asset and implements the following new ones.

auto_upgrade

my $upgrade = $mem->auto_upgrade;
$mem        = $mem->auto_upgrade(1);

Try to detect if content size exceeds max_memory_size limit and automatically upgrade to a Mojo::Asset::File object.

max_memory_size

my $size = $mem->max_memory_size;
$mem     = $mem->max_memory_size(1024);

Maximum size in bytes of data to keep in memory before automatically upgrading to a Mojo::Asset::File object, defaults to the value of the MOJO_MAX_MEMORY_SIZE environment variable or 262144.

METHODS

Mojo::Asset::Memory inherits all methods from Mojo::Asset and implements the following new ones.

new

my $mem = Mojo::Asset::Memory->new;

Construct a new Mojo::Asset::Memory object.

add_chunk

$mem     = $mem->add_chunk('foo bar baz');
my $file = $mem->add_chunk('abc' x 262144);

Add chunk of data and upgrade to Mojo::Asset::File object if necessary.

contains

my $position = $mem->contains('bar');

Check if asset contains a specific string.

get_chunk

my $bytes = $mem->get_chunk($offset);
my $bytes = $mem->get_chunk($offset, $max);

Get chunk of data starting from a specific position, defaults to a maximum chunk size of 131072 bytes.

move_to

$mem = $mem->move_to('/home/sri/foo.txt');

Move asset data into a specific file.

size

my $size = $mem->size;

Size of asset data in bytes.

slurp

my $bytes = mem->slurp;

Read all asset data at once.

SEE ALSO

Mojolicious, Mojolicious::Guides, http://mojolicio.us.