Apollo Router Operation Limits Vulnerable to Bypass via Integer Overflow
Package
Affected versions
<1.61.2
>=2.0.0-alpha.0 <2.1.1
Patched versions
1.61.2
2.1.1
apollographql/helm-charts/router
(GitHub Packages Container Registry)
<1.61.2
>=2.0.0-alpha.0 <2.1.1
1.61.2
2.1.1
apollographql/router
(GitHub Packages Container Registry)
<1.61.2
>=2.0.0-alpha.0 <2.1.1
1.61.2
2.1.1
apollographql/router
(GitHub Releases)
<1.61.2
>=2.0.0-alpha.0 <2.1.1
1.61.2
2.1.1
Impact
Summary
A vulnerability in Apollo Router allowed certain queries to bypass configured operation limits, specifically due to integer overflow.
Details
The operation limits plugin uses unsigned 32-bit integers to track limit counters (e.g. for a query's height). If a counter exceeded the maximum value for this data type (4,294,967,295), it wrapped around to 0, unintentionally allowing queries to bypass configured thresholds. This could occur for large queries if the payload limit were sufficiently increased, but could also occur for small queries with deeply nested and reused named fragments.
Fix/Mitigation
Logic was updated to ensure counter overflow is handled correctly and does not wrap around to 0.
Patches
This has been remediated in
apollo-routerversions 1.61.2 and 2.1.1.Workarounds
The only known workaround is "Safelisting" or "Safelisting with IDs only" per Safelisting with Persisted Queries - Apollo GraphQL Docs.
Acknowledgements
We appreciate the efforts of the security community in identifying and improving the performance and security of operation limiting mechanisms.