Laravel Reverb missing Pusher-compatible API signature verification

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2024-50347?

CVE-2024-50347 is a vulnerability classified as Improper Verification of Cryptographic Signature, affecting reverb (affected versions: < 1.4.0). This vulnerability is rated Medium, with a CVSS score of 6.3. Current sources do not report this vulnerability as exploited.

Overview

Original source data

Laravel Reverb provides a real-time WebSocket communication backend for Laravel applications. Prior to 1.4.0, there is an issue where verification signatures for requests sent to Reverb's Pusher-compatible API were not being verified. This API is used in scenarios such as broadcasting a message from a backend service or for obtaining statistical information (such as number of connections) about a given channel. This issue only affects the Pusher-compatible API endpoints and not the WebSocket connections themselves. In order to exploit this vulnerability, the application ID which, should never be exposed, would need to be known by an attacker. This vulnerability is fixed in 1.4.0.

Affected products and scope

  • laravel/reverb versions < 1.4.0 are affected.
  • The identified patched version is 1.4.0.
  • The affected scope is Reverb's Pusher-compatible API endpoints. WebSocket connections are not affected according to the technical description.
  • The record provides no additional parallel branches or deployment conditions beyond the < 1.4.0 boundary. The status of other branches is left unknown.

Technical details

Laravel Reverb uses an authentication signature generated from request components and the application's secret key. The Pusher-compatible API is expected to regenerate the signature and allow the request only when the supplied and regenerated values match, but affected releases before 1.4.0 did not consistently perform that verification. The patch makes the API controller flow call verifySignature and treats a missing auth_signature as an invalid signature. The identified affected endpoints are POST /events, POST /events_batch, GET /connections, GET /channels, GET /channel, GET /channel_users, and POST /users_terminate. Exploitation requires network access to these endpoints and knowledge of the application ID, which the advisory says should not be exposed; the record does not establish how that value would be disclosed or the full data scope of every operation.

Exploitability

The vulnerable surface is network-reachable when the Pusher-compatible API is deployed and accessible. The record indicates that no authenticated privilege and no separate user interaction are required, but the attacker must know the application ID, making exploitation dependent on a deployment-specific value. The affected scope is limited to the Pusher-compatible API endpoints and does not include the WebSocket connections themselves. The supplied record does not document known exploitation or a public exploit; that limitation should not be interpreted as proof that exploitation has never occurred outside the available evidence.

Technical impact

The flaw weakens the mechanism that authenticates the origin of Pusher-compatible API requests with a cryptographic signature. An attacker who meets the application ID condition may cause Reverb to process API requests that should have been rejected because their signatures are invalid, potentially affecting broadcast integrity and exposing some channel statistics. The advisory does not extend the impact directly to WebSocket connections, and the record does not confirm code execution, server takeover, or loss of availability. Actual consequences depend on which endpoints are exposed, what channel data the application manages, and how it uses the API operations.

Business impact

If the affected API is exposed and the application ID is known, an organization could face the following consequences:

  • Real-time messages could be broadcast to a channel without a valid signature, resulting in false or unwanted notifications for clients.
  • Operational statistics such as a channel's connection count could be queried without authorization, exposing limited deployment information depending on the application's data and configuration.
  • Other administrative API operations within the affected endpoint set could be invoked without the intended authorization check; the available evidence does not fully define the business effect or scope of each operation.
  • Direct WebSocket connections are outside the stated scope of the flaw, so this issue should not be treated as a failure of authentication for the entire WebSocket channel.

Remediation

  1. Upgrade laravel/reverb to 1.4.0, the release identified as fixing the API signature verification issue.
  2. After upgrading, verify the version in the deployed artifact and composer.lock, then test the Pusher-compatible API in staging.
  3. Review network access to the Pusher-compatible API endpoints and restrict them to trusted backend services where the application architecture permits. This is a precautionary control, not a vendor-confirmed substitute for the patch.
  4. Protect the application ID from public clients, public documentation, and unnecessary logs or telemetry because knowledge of this value is the exploitation condition described by the advisory.
  5. If an upgrade is not immediately possible, do not treat endpoint hiding or selective request blocking as equivalent to a fix. The record does not provide a confirmed vendor mitigation that replaces the update.

Detection

  1. Inventory Laravel applications that install laravel/reverb and determine the deployed version from composer.lock, images, or release artifacts.
  2. Identify deployments that enable or expose the events, events_batch, connections, channels, channel, channel_users, and users_terminate endpoints of the Pusher-compatible API.
  3. Review reverse-proxy, gateway, and application logs for requests to those endpoints, especially requests that do not originate from expected backend services. Treat this as precautionary monitoring, not as a vendor-confirmed indicator.
  4. Check how the application ID is stored and distributed, and verify that it is not present in public clients, public documentation, or unnecessary telemetry.
  5. Do not treat the absence of suspicious log entries as proof of safety. Correlate log review with the installed package version and the actual exposed API surface.
Sources (22)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.