/ 
Mojolicious-7.89
River stage four • 1088 direct dependents • 1233 total dependents
⭐ Starred 2674 GitHub stars
/ Mojo::IOLoop::Stream::WebSocketClient
Security Advisories (7)
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.

CPANSA-Mojolicious-2018-04 (2018-08-09)

This release reverts the addition of stream classes (added in 7.83), which have unfortunately resulted in many Mojolicious applications becoming unstable. While there are no known exploits yet, we've chosen to err on the side of cautiousness and will classify this as a security issue.

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.

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.

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

Mojolicious versions from 7.28 for Perl may generate weak HMAC session secrets. When creating a default app 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.

NAME

Mojo::IOLoop::Stream::WebSocketClient - Non-blocking I/O WebSocket client stream

SYNOPSIS

use Mojo::IOLoop::Stream::WebSocketClient;
use Mojo::Transaction::WebSocket;

# Create transaction
my $ws = Mojo::Transaction::WebSocket->new;
$ws->on(message => sub {
  my ($ws, $msg) = @_;
  say "Message: $msg";
});

# Create stream and process transaction with it
my $stream = Mojo::IOLoop::Stream::WebSocketClient->new($handle);
$stream->process($ws);

# Start reactor if necessary
$stream->reactor->start unless $stream->reactor->is_running;

DESCRIPTION

Mojo::IOLoop::Stream::WebSocketClient is a container for I/O streams used by Mojo::IOLoop to support the WebSocket protocol client-side.

EVENTS

Mojo::IOLoop::Stream::WebSocketClient inherits all events from Mojo::IOLoop::Stream::HTTPClient.

ATTRIBUTES

Mojo::IOLoop::Stream::WebSocketClient inherits all attributes from Mojo::IOLoop::Stream::HTTPClient.

METHODS

Mojo::IOLoop::Stream::WebSocketClient inherits all methods from Mojo::IOLoop::Stream::HTTPClient and implements the following new ones.

process

$stream->process(Mojo::Transaction::WebSocket->new);

Process a Mojo::Transaction::WebSocket object.

SEE ALSO

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