GHSA-JG2J-VMC9-5M2P
Reverb max_connections limit bypass allows unauthenticated connection exhaustion
Texto original en inglés · Ver en español
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-JG2J-VMC9-5M2P divulgada | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Impact
Laravel Reverb applications that configure a `max_connections` limit do not reliably enforce it. When a connection is rejected for exceeding the limit, Reverb sends an error but leaves the WebSocket open and usable. Connections that have not subscribed to any channel are also not counted toward the limit and are not seen by the ping and prune jobs. An unauthenticated remote client that knows the public application key can hold many connections open and exhaust server resources, causing denial of service.
Patches
Fixes are proposed in laravel/reverb pull requests #419 (closes connections rejected on open) and #422 (tracks all open connections for limit enforcement, ping and prune). Neither has been confirmed as merged or released.
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
Packagistlaravel/reverb |
Corregida | 1.14.0 | — | — |
1.14.0Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/laravel/reverb/security/advisories/GHSA-jg2j-vmc9-5m2pLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
