p PatchFirst

CVE-2024-50347

CVE-2024-50347 · Laravel Reverb has Missing API Signature Verification

This page contains facts from public vulnerability sources. Check the original advisory before updating.

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.

CVSS 6.3 · Medium · EPSS 0.3% · Fix available

Published
Updated

Stack: php

Affected products and versions

  • reverb

    Versions
    • < 1.4.0: Affected

    No fix published

  • laravel/reverb Packagist

    Versions
    • v1.0.0
    • v1.0.0-beta1
    • v1.0.0-beta10
    • v1.0.0-beta11
    • v1.0.0-beta12
    • v1.0.0-beta13
    • v1.0.0-beta14
    • v1.0.0-beta2
    • v1.0.0-beta3
    • v1.0.0-beta4
    • v1.0.0-beta5
    • v1.0.0-beta6
    • v1.0.0-beta7
    • v1.0.0-beta8
    • v1.0.0-beta9
    • v1.1.0
    • v1.2.0
    • v1.3.0
    • v1.3.1
    Affected ranges
    • ECOSYSTEM: < 1.4.0

    Update to 1.4.0

Original sources

Check your server →