Vulnerability · Published Oct 31, 2024 · Assigned by GitHub_M

CVE-2024-50347Laravel Reverb has Missing API Signature Verification

Medium 6.3

In plain English

A medium-severity security flaw in reverb from laravel. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 28% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 4.0)6.3Medium
Exploit odds (30 days)0.3%top 71.7% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

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 packages & fixed versions

EcosystemPackageFixed inAdvisory
Packagistlaravel/reverb1.4.0GHSA-pfrr-xvrf-pxjx

Affected products (as reported)

VendorProductVersions
laravel reverb < 1.4.0

Weakness: CWE-347 · Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/U:Green

References