/ 
Mojolicious-7.46
⭐ Starred 2674 / Mojo::Cookie
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-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.

CVE-2024-58135 (2025-05-03)

Mojolicious versions from 7.28 through 9.45 for Perl will generate weak HMAC session cookie secrets via "mojo generate app" by default. When creating a default app skeleton with the "mojo generate app" tool, a weak secret is written to the application's configuration file using the insecure rand() function, and used for authenticating and protecting the integrity of the application's sessions. This may allow an attacker to brute force the application's session keys. Release 9.46 fixes the issue by providing high quality randomness, even in absence of CryptX. Users should be aware that the update does not replace previously generated weak secrets. A secret generated with the previous version MUST be replaced to ensure the updated version is using a strong secret.

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::Cookie - HTTP cookie base class

SYNOPSIS

package Mojo::Cookie::MyCookie;
use Mojo::Base 'Mojo::Cookie';

sub parse     {...}
sub to_string {...}

DESCRIPTION

Mojo::Cookie is an abstract base class for HTTP cookie containers, based on RFC 6265, like Mojo::Cookie::Request and Mojo::Cookie::Response.

ATTRIBUTES

Mojo::Cookie implements the following attributes.

name

my $name = $cookie->name;
$cookie  = $cookie->name('foo');

Cookie name.

value

my $value = $cookie->value;
$cookie   = $cookie->value('/test');

Cookie value.

METHODS

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

parse

my $cookies = $cookie->parse($str);

Parse cookies. Meant to be overloaded in a subclass.

to_string

my $str = $cookie->to_string;

Render cookie. Meant to be overloaded in a subclass.

OPERATORS

Mojo::Cookie overloads the following operators.

bool

my $bool = !!$cookie;

Always true.

stringify

my $str = "$cookie";

Alias for "to_string".

SEE ALSO

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