Medium severity · published Oct 31, 2024
CVE-2024-50347
Laravel Reverb has Missing API Signature Verification
6.3
CVSS
0.3%
EPSS
No
On KEV
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.
Exploitation
Is it being used?
Exploit prediction (EPSS)0.3% · higher than 28% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
RE
reverb · laravel
< 1.4.0 · source: vendor
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2024-50347
CVE.org
https://www.cve.org/CVERecord?id=CVE-2024-50347
github.com
https://github.com/laravel/reverb/commit/73cc140d76e803b151fc2dd2e4eb3eb784a82ee2
github.com
https://github.com/laravel/reverb/pull/252
github.com
https://github.com/laravel/reverb/releases/tag/v1.4.0
github.com
https://github.com/laravel/reverb/security/advisories/GHSA-pfrr-xvrf-pxjx
More from reverb
9.8
CVE-2026-23524
Laravel Redis Horizontal Scaling Insecure Deserialization
