We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.

Please see our statement on Data Privacy.

Crisp.chat (Helpdesk and Chat)

Ok

THREATINT
PUBLISHED

CVE-2024-50347

Laravel Reverb has Missing API Signature Verification



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.

Reserved 2024-10-22 | Published 2024-10-31 | Updated 2024-10-31 | Assigner GitHub_M


MEDIUM: 6.3CVSS: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

Problem types

CWE-347: Improper Verification of Cryptographic Signature

Product status

< 1.4.0
affected

References

github.com/...reverb/security/advisories/GHSA-pfrr-xvrf-pxjx

github.com/laravel/reverb/pull/252

github.com/...ommit/73cc140d76e803b151fc2dd2e4eb3eb784a82ee2

github.com/laravel/reverb/releases/tag/v1.4.0

cve.org (CVE-2024-50347)

nvd.nist.gov (CVE-2024-50347)

Download JSON

Share this page
https://cve.threatint.com/CVE/CVE-2024-50347

Support options

Helpdesk Chat, Email, Knowledgebase
Telegram Chat
Subscribe to our newsletter to learn more about our work.