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::Content::Single - HTTP 1.1 content container

SYNOPSIS

use Mojo::Content::Single;

my $single = Mojo::Content::Single->new;
$single->parse("Content-Length: 12\r\n\r\nHello World!");

DESCRIPTION

Mojo::Content::Single is a container for HTTP 1.1 content as described in RFC 2616.

EVENTS

Mojo::Content::Single inherits all events from Mojo::Content and can emit the following new ones.

upgrade

$single->on(upgrade => sub {
  my ($single, $multi) = @_;
});

Emitted when content gets upgraded to a Mojo::Content::MultiPart object. Note that this event is EXPERIMENTAL and might change without warning!

$single->on(upgrade => sub {
  my ($single, $multi) = @_;
  return unless $multi->headers->content_type =~ /multipart\/([^;]+)/i;
  say "Multipart: $1";
});

ATTRIBUTES

Mojo::Content::Single inherits all attributes from Mojo::Content and implements the following new ones.

asset

my $asset = $single->asset;
$single   = $single->asset(Mojo::Asset::Memory->new);

The actual content, defaults to a Mojo::Asset::Memory object.

auto_upgrade

my $upgrade = $single->auto_upgrade;
$single     = $single->auto_upgrade(0);

Try to detect multipart content and automatically upgrade to a Mojo::Content::MultiPart object, defaults to 1. Note that this attribute is EXPERIMENTAL and might change without warning!

METHODS

Mojo::Content::Single inherits all methods from Mojo::Content and implements the following new ones.

body_contains

my $success = $single->body_contains('1234567');

Check if content contains a specific string.

body_size

my $size = $single->body_size;

Content size in bytes.

clone

my $clone = $single->clone;

Clone content if possible. Note that this method is EXPERIMENTAL and might change without warning!

get_body_chunk

my $chunk = $single->get_body_chunk(0);

Get a chunk of content starting from a specfic position.

parse

$single   = $single->parse("Content-Length: 12\r\n\r\nHello World!");
my $multi = $single->parse("Content-Type: multipart/form-data\r\n\r\n");

Parse content chunk and upgrade to Mojo::Content::MultiPart object if possible.

SEE ALSO

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