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 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

Mojolicious::Routes::Match - Find routes

SYNOPSIS

use Mojolicious::Controller;
use Mojolicious::Routes;
use Mojolicious::Routes::Match;

# Routes
my $r = Mojolicious::Routes->new;
$r->get('/:controller/:action');
$r->put('/:controller/:action');

# Match
my $c = Mojolicious::Controller->new;
my $match = Mojolicious::Routes::Match->new(root => $r);
$match->match($c => {method => 'PUT', path => '/foo/bar'});
say $match->stack->[0]{controller};
say $match->stack->[0]{action};

# Render
say $match->path_for->{path};
say $match->path_for(action => 'baz')->{path};

DESCRIPTION

Mojolicious::Routes::Match finds routes in Mojolicious::Routes structures.

ATTRIBUTES

Mojolicious::Routes::Match implements the following attributes.

current

my $current = $match->current;
$match      = $match->current(2);

Current position on the "stack", defaults to 0.

endpoint

my $endpoint = $match->endpoint;
$match       = $match->endpoint(Mojolicious::Routes::Route->new);

The route endpoint that matched, usually a Mojolicious::Routes::Route objects.

root

my $root = $match->root;
$match   = $match->root(Mojolicious::Routes->new);

The root of the route structure, usually a Mojolicious::Routes object.

stack

my $stack = $match->stack;
$match    = $match->stack([{foo => 'bar'}]);

Captured parameters with nesting history.

METHODS

Mojolicious::Routes::Match inherits all methods from Mojo::Base and implements the following new ones.

match

$match->match(Mojolicious::Controller->new, {method => 'GET', path => '/'});

Match controller and options against "root" to find appropriate "endpoint".

path_for

my $info = $match->path_for;
my $info = $match->path_for(foo => 'bar');
my $info = $match->path_for({foo => 'bar'});
my $info = $match->path_for('named');
my $info = $match->path_for('named', foo => 'bar');
my $info = $match->path_for('named', {foo => 'bar'});

Render matching route with parameters into path.

SEE ALSO

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