Overview
- 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.
- Source
- security-advisories@github.com
- NVD status
- Awaiting Analysis
Risk scores
CVSS 4.0
- Type
- Secondary
- Base score
- 6.3
- Impact score
- -
- Exploitability score
- -
- Vector string
- 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:Green
- Severity
- MEDIUM
Weaknesses
- security-advisories@github.com
- CWE-347
Social media
- Hype score
- Not currently trending
CVE-2024-50347 Unverified Request Signatures in Laravel Reverb Pusher API Prior to 1.4.0 Laravel Reverb is used for real-time WebSocket communication in Laravel apps. Before version 1.4.0, there was a problem. Th... https://t.co/YVQNTWkYbe
@VulmonFeeds
31 Oct 2024
54 Impressions
0 Retweets
0 Likes
0 Bookmarks
0 Replies
0 Quotes
CVE-2024-50347 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 requ… https://t.co/5PlbHsoitP
@CVEnew
31 Oct 2024
359 Impressions
0 Retweets
0 Likes
0 Bookmarks
0 Replies
0 Quotes