CVE-2024-50347 Laravel Reverb has Missing API Signature Verification
Attackers can bypass API signature verification to broadcast messages or read channel statistics if the application ID is known.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2024-50347?
CVE-2024-50347 is a medium-severity missing authorization vulnerability in laravel reverb, published on 31 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
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.
Weakness: CWE-347
Which versions are affected by CVE-2024-50347?
2 open source packages ship an affected version, including laravel/reverb.
| Package | Affected | Fixed in |
|---|---|---|
laravel/reverb Packagist | All versions | 1.4.0 |
laravel/reverb Packagist | All versions | 1.4.0 |
How do I fix CVE-2024-50347?
Upgrade laravel/reverb to 1.4.0 or later.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2024-50347 being exploited?
There is no known exploitation of CVE-2024-50347 in the wild and no public exploit code.
Sources
Also known as GHSA-pfrr-xvrf-pxjx.