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::IOLoop::Client - IOLoop socket client

SYNOPSIS

use Mojo::IOLoop::Client;

# Create socket connection
my $client = Mojo::IOLoop::Client->new;
$client->on(connect => sub {
  my ($client, $handle) = @_;
  ...
});
$client->on(error => sub {
  my ($client, $error) = @_;
  ...
});
$client->connect(address => 'mojolicio.us', port => 80);

DESCRIPTION

Mojo::IOLoop::Client performs non-blocking socket connections for Mojo::IOLoop. Note that this module is EXPERIMENTAL and might change without warning!

EVENTS

Mojo::IOLoop::Client can emit the following events.

connect

$client->on(connect => sub {
  my ($client, $handle) = @_;
});

Emitted once the connection is established.

error

$client->on(error => sub {
  my ($client, $error) = @_;
});

Emitted if an error happens on the connection.

ATTRIBUTES

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

resolver

my $resolver = $client->resolver;
$client      = $client->resolver(Mojo::IOLoop::Resolver->new);

DNS stub resolver, defaults to a Mojo::IOLoop::Resolver object.

METHODS

Mojo::IOLoop::Client inherits all methods from Mojo::EventEmitter and implements the following new ones.

connect

$client->connect(
  address => '127.0.0.1',
  port    => 3000
);

Open a socket connection to a remote host. Note that TLS support depends on IO::Socket::SSL and IPv6 support on IO::Socket::IP.

These options are currently available:

address

Address or host name of the peer to connect to.

handle

Use an already prepared handle.

port

Port to connect to.

tls

Enable TLS.

tls_cert

Path to the TLS certificate file.

tls_key

Path to the TLS key file.

SEE ALSO

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