GHSA-W5F8-87H2-M573
Request/Response inbound failure retains stale `response_channels` state after attacker-controlled failed requests
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-W5F8-87H2-M573 divulgada | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
### Impact
The inbound request/response path in `network-libp2p` stores a `request_id -> response_channel` entry for response-bearing requests before dispatching them to the application handler. If the same request later ends in `request_response::Event::InboundFailure`, the failure handler only logs and never removes the saved entry.
This creates a fail-open state lifecycle. Successful responses explicitly reclaim `response_channels`, but failed inbound requests do not. A remote peer can therefore send normal response-bearing request/response traffic and repeatedly force the failed-request path so that stale bookkeeping entries accumulate over time.
### Patches
The patch for this vulnerability https://github.com/nimiq/core-rs-albatross/pull/3665 is formally released as part of v1.3.0 https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0.
### Workarounds
No known workarounds.
### References
See PR https://github.com/nimiq/core-rs-albatross/pull/3665.
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
crates.ionimiq-network-libp2p |
Sin parche | — | — | — |
Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-w5f8-87h2-m573Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
