Laravel reverb up to 1.3.x API Endpoint signature verification

Summaryinfo

A vulnerability was found in Laravel reverb up to 1.3.x. It has been declared as problematic. The impacted element is an unknown function of the component API Endpoint. Executing a manipulation can lead to signature verification. This vulnerability is tracked as CVE-2024-50347. The attack can be launched remotely. No exploit exists. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in Laravel reverb up to 1.3.x. It has been declared as problematic. This vulnerability affects some unknown processing of the component API Endpoint. The manipulation with an unknown input leads to a signature verification vulnerability. The CWE definition for the vulnerability is CWE-347. The product does not verify, or incorrectly verifies, the cryptographic signature for data. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is shared for download at github.com. This vulnerability was named CVE-2024-50347 since 10/22/2024. The exploitation appears to be difficult. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are neither technical details nor an exploit publicly available.

Upgrading to version 1.4.0 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 73cc140d76e803b151fc2dd2e4eb3eb784a82ee2 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• Laravel

Name

• reverb

Version

• 1.0
• 1.1
• 1.2
• 1.3

License

• open-source

Website

• Product: https://github.com/laravel/reverb/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion