Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2024-50347 Overview
Laravel Reverb provides a real-time WebSocket communication backend for Laravel applications. The framework exposes a Pusher-compatible HTTP API used for broadcasting messages from backend services and retrieving channel statistics. Versions prior to 1.4.0 fail to verify request signatures on this API, allowing attackers who possess the application ID to issue unauthenticated administrative requests. The WebSocket connections themselves are not affected by this flaw. The maintainers tracked the issue under advisory GHSA-pfrr-xvrf-pxjx and released a fix in version 1.4.0. The weakness is classified as improper verification of cryptographic signature [CWE-347].
Critical Impact
Attackers who learn the application ID can broadcast arbitrary messages to WebSocket channels and query channel metadata by bypassing signature validation on Reverb's Pusher-compatible HTTP API.
Affected Products
- Laravel Reverb versions prior to 1.4.0
- Applications exposing Reverb's Pusher-compatible HTTP API endpoints
- Backend services broadcasting through Reverb using Pusher protocol semantics
Discovery Timeline
- 2024-10-31 - CVE-2024-50347 published to the National Vulnerability Database
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2024-50347
Vulnerability Analysis
Laravel Reverb implements a Pusher-compatible HTTP API to let server-side code broadcast events and query channel state. The Pusher protocol defines an HMAC-SHA256 signature scheme where each request is signed using the application's secret key. Reverb accepted these requests but never validated the auth_signature parameter against the expected value. An attacker who knows the application ID can therefore send crafted HTTP requests to broadcast arbitrary payloads to any channel or enumerate channel statistics. Exploitation requires knowledge of the application ID, which is not treated as a secret in Pusher's threat model and may leak through logs, configuration files, or client bundles. The vulnerability is categorized under [CWE-347] Improper Verification of Cryptographic Signature.
Root Cause
The HTTP controller handling Pusher API requests invoked setApplication() and setChannels() but never called a signature verification routine. The patch introduces verifySignature($request) into the controller's initialization flow, enforcing the HMAC check that the Pusher protocol specification requires.
Attack Vector
An attacker reaches the Reverb HTTP endpoint over the network, submits a POST request to a Pusher-compatible route such as /apps/{appId}/events, and supplies an invalid or missing auth_signature. Vulnerable servers accept the request and broadcast the attacker-supplied payload to all subscribers of the targeted channel.
// Patch applied in src/Protocols/Pusher/Http/Controllers/Controller.php
$this->setApplication($appId);
$this->setChannels();
+ $this->verifySignature($request);
}
Source: Laravel Reverb commit 73cc140
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2024-50347
Indicators of Compromise
- Unexpected broadcast events appearing on WebSocket channels without a corresponding backend trigger
- HTTP requests to /apps/{appId}/events or /apps/{appId}/channels endpoints with malformed or missing auth_signature query parameters
- Access-log entries from unfamiliar source IPs targeting Reverb's Pusher-compatible routes
Detection Strategies
- Parse Reverb HTTP access logs for requests to Pusher API paths and compare the auth_signature parameter against an HMAC computed from the known application secret
- Correlate backend broadcast activity with WebSocket events delivered to clients to identify broadcasts without a legitimate server origin
- Alert on any Reverb installation running a version below 1.4.0 identified through software inventory
Monitoring Recommendations
- Centralize Reverb HTTP and WebSocket logs in a SIEM for retrospective hunting against the indicators above
- Monitor egress and ingress traffic to the Reverb HTTP port for sources outside expected backend service ranges
- Track channel subscription counts and message volume for anomalies that may indicate unauthorized broadcasts
How to Mitigate CVE-2024-50347
Immediate Actions Required
- Upgrade Laravel Reverb to version 1.4.0 or later, which enforces signature verification on all Pusher-compatible API requests
- Rotate the Reverb application ID and secret if signs of exposure or exploitation are present
- Restrict network access to the Reverb HTTP API so that only trusted backend services can reach the Pusher-compatible endpoints
Patch Information
The fix is included in Laravel Reverb v1.4.0 via pull request #252. Full technical context is available in the GHSA-pfrr-xvrf-pxjx security advisory. Upgrade using Composer with composer require laravel/reverb:^1.4.0 and restart the Reverb service.
Workarounds
- Place Reverb's HTTP API behind a reverse proxy or firewall rule that limits inbound connections to known backend service IP addresses
- Treat the application ID as a secret by removing it from client-side bundles, public configuration files, and version control
- Terminate inbound Pusher API traffic at an API gateway that validates the HMAC auth_signature before forwarding to Reverb
# Composer upgrade to the patched release
composer require laravel/reverb:^1.4.0
php artisan config:clear
php artisan reverb:restart
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

