GHSA-M5Q4-Q9RR-M3VR
Apollo Router Demand Control Vulnerable to Cost-Limit Bypass via Negative and Oversized List Sizes
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Fuente: GitHub
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-M5Q4-Q9RR-M3VR divulgada · CVSS 7.5 (GitHub) | |
| Remediación | Parche 2.10.5 | apollo-router · 0 d desde divulgación | |
| Remediación | Parche 2.16.1 | apollo-router · 0 d desde divulgación | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Impact
Summary
A vulnerability in Apollo Router allowed certain operations to bypass configured demand control cost limits. A client-supplied `@listSize` slicing argument provided as a negative value — and, separately, a configured list size exceeding the signed 32-bit integer range — could drive an operation's estimated cost negative, letting operations that should exceed a configured maximum cost pass enforcement.
Details
Demand control estimates an operation's cost before execution and, in enforce mode, rejects operations whose estimated cost exceeds a configured maximum. The `@listSize` directive's slicing arguments (for example `first`) are read from the client's operation to size list fields when estimating cost.
Negative slicing values were used unchanged, producing a negative contribution to the estimate. Because the costs of sibling fields are summed, a negative-sized selection could offset the cost of an otherwise-expensive operation and bring the total estimate below the configured maximum, while the expensive portion of the operation still executed. Separately, a configured `list_size` above the signed 32-bit integer range could wrap to a negative value with the same effect.
Who Is Impacted
Operators using Apollo Router demand control in enforce mode. Demand control is opt-in; operators who have not enabled it are not affected.
Fix
List sizes are now bounded to non-negative values before cost is computed: negative slicing arguments are clamped to zero, and configured list sizes use a saturating conversion. An operation's estimated cost can no longer be driven below zero.
Patches
This has been remediated in `apollo-router` versions 2.10.5 and 2.16.1.
Workarounds
Demand control is opt-in, so operators who have not enabled it are not affected. There is no configuration-based workaround for operators relying on demand control; affected operators should upgrade to a patched version.
Acknowledgements
We appreciate the efforts of the security community in identifying and improving the security of Apollo Router's demand control mechanisms.
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
crates.ioapollo-router |
Corregida | 2.10.5, 2.16.1 | 0 d · 0 d | 2.19.0 no afectada |
2.10.52.16.1Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/apollographql/router/security/advisories/GHSA-m5q4-q9rr-m3vrLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
