Security Advisories (11)
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-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-03 (2018-05-19)

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

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

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

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-2014-01 (2014-10-07)

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

CVE-2026-14803 (2026-07-06)

Mojo::JSON versions before 9.47 for Perl allow memory exhaustion via unbounded recursion in the pure-Perl decoder. The pure-Perl decode path (`_decode_value` dispatching to `_decode_array` and `_decode_object`) recurses with no depth limit, so a small deeply nested JSON document can consume excessive memory. This path is the default when Cpanel::JSON::XS is not installed or `MOJO_NO_JSON_XS=1` is set; the Cpanel::JSON::XS fast path is not affected. Any caller that decodes an untrusted JSON body, for example `Mojo::Message::json` reached through `$c->req->json`, can exhaust process memory and cause denial of service.

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.

NAME

Mojo::IOWatcher - Non-blocking I/O watcher

SYNOPSIS

use Mojo::IOWatcher;

# Watch if I/O handles become readable or writable
my $watcher = Mojo::IOWatcher->new;
$watcher->add($handle, on_readable => sub {
  my ($watcher, $handle) = @_;
  ...
});

# Use timers
$watcher->timer(15 => sub {
  my $watcher = shift;
  $watcher->remove($handle);
  say "Timeout!";
});

# Start and stop watcher
$watcher->start;
$watcher->stop;

DESCRIPTION

Mojo::IOWatcher is a minimalistic non-blocking I/O watcher and the foundation of Mojo::IOLoop. Mojo::IOWatcher::EV is a good example for its extensibility. Note that this module is EXPERIMENTAL and might change without warning!

METHODS

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

add

$watcher = $watcher->add($handle, on_readable => sub {...});

Add handles and watch for I/O events.

These options are currently available:

on_readable

Callback to be invoked once the handle becomes readable.

on_writable

Callback to be invoked once the handle becomes writable.

cancel

my $success = $watcher->cancel($id);

Cancel timer.

detect

my $class = Mojo::IOWatcher->detect;

Detect and load the best watcher implementation available, will try the value of the MOJO_IOWATCHER environment variable or Mojo::IOWatcher::EV. Note that this method is EXPERIMENTAL and might change without warning!

is_readable

my $success = $watcher->is_readable($handle);

Quick check if a handle is readable, useful for identifying tainted sockets.

not_writing

$watcher = $watcher->not_writing($handle);

Only watch handle for readable events.

recurring

my $id = $watcher->recurring(3 => sub {...});

Create a new recurring timer, invoking the callback repeatedly after a given amount of seconds.

remove

$watcher = $watcher->remove($handle);

Remove handle.

start

$watcher->start;

Start watching for I/O and timer events.

stop

$watcher->stop;

Stop watching for I/O and timer events.

timer

my $id = $watcher->timer(3 => sub {...});

Create a new timer, invoking the callback after a given amount of seconds.

writing

$watcher = $watcher->writing($handle);

Watch handle for readable and writable events.

DEBUGGING

You can set the MOJO_IOWATCHER_DEBUG environment variable to get some advanced diagnostics information printed to STDERR.

MOJO_IOWATCHER_DEBUG=1

SEE ALSO

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