Security Advisories (8)
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-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

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::IOLoop::Subprocess - Subprocesses

SYNOPSIS

use Mojo::IOLoop::Subprocess;

# Operation that would block the event loop for 5 seconds
my $subprocess = Mojo::IOLoop::Subprocess->new;
$subprocess->run(
  sub {
    my $subprocess = shift;
    sleep 5;
    return '♥', 'Mojolicious';
  },
  sub {
    my ($subprocess, $err, @results) = @_;
    say "Subprocess error: $err" and return if $err;
    say "I $results[0] $results[1]!";
  }
);

# Start event loop if necessary
$subprocess->ioloop->start unless $subprocess->ioloop->is_running;

DESCRIPTION

Mojo::IOLoop::Subprocess allows Mojo::IOLoop to perform computationally expensive operations in subprocesses, without blocking the event loop.

ATTRIBUTES

Mojo::IOLoop::Subprocess implements the following attributes.

deserialize

my $cb      = $subprocess->deserialize;
$subprocess = $subprocess->deserialize(sub {...});

A callback used to deserialize subprocess return values, defaults to using Storable.

$subprocess->deserialize(sub {
  my $bytes = shift;
  return [];
});

ioloop

my $loop    = $subprocess->ioloop;
$subprocess = $subprocess->ioloop(Mojo::IOLoop->new);

Event loop object to control, defaults to the global Mojo::IOLoop singleton.

serialize

my $cb      = $subprocess->serialize;
$subprocess = $subprocess->serialize(sub {...});

A callback used to serialize subprocess return values, defaults to using Storable.

$subprocess->serialize(sub {
  my $array = shift;
  return '';
});

METHODS

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

pid

my $pid = $subprocess->pid;

Process id of the spawned subprocess if available.

run

$subprocess = $subprocess->run(sub {...}, sub {...});

Execute the first callback in a child process and wait for it to return one or more values, without blocking "ioloop" in the parent process. Then execute the second callback in the parent process with the results. The return values of the first callback and exceptions thrown by it, will be serialized with Storable, so they can be shared between processes.

SEE ALSO

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