Vulnerability Intelligence Report
Laravel Reverb has Missing API Signature Verification
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 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.
No Active Exploit Signals
CVSS Base Score
6.3
MEDIUM
EPSS Probability:0.33%
Executive Threat Verdict
Evaluating...
Evaluating Threat Landscape...
Assessing known weaponization, exploitation telemetry, and federal advisories.
Attack Surface
—
Authentication
—
Weaponization
—
SSVC Action
—
Weaknesses (CWE)
CWE-347 ↗CWE-347: Improper Verification of Cryptographic Signature
Affected Products & Versions
| Vendor | Product | Affected Versions |
|---|---|---|
| laravel | reverb | < 1.4.0 (affected) |
References & Technical Advisories
No reference links found.
Threat Intelligence Signals
EPSS Score
0.332%
GitHub Advisory
Identity & Timeline
| Status | PUBLISHED |
| Assigning Authority | GitHub, Inc. · Vendor · USA |
| Reserved | 2024-10-22T17:54:40 |
| Published | 2024-10-31T17:56:41 |
| Last Updated | 2024-10-31T19:46:33 |
Community Chatter & Buzz