Packages / @apollo/gateway / Security
Apollo Gateway Query Planner Vulnerable to Excessive Resource Consumption via Named Fragment Expansion
Affected releases · @apollo/gateway
- 2.x2.0.0 – 2.10.0Fixed in 2.10.1
- 0.54.x and older0.1.0 – 0.54.1No fix, no longer updated
On 2.x, the newest line:
npm install @apollo/gateway@2.10.1Affected
2.0.0 – 2.10.0
71 releases
Fixed
2.10.1 – 2.14.4
28 releases, latest
Affected
0.1.0 – 0.54.1
152 releases
Is your project affected?
Paste your package.json, or type the range you declare for @apollo/gateway. It is read in your browser and sent nowhere.
What happens
Impact
Summary
A vulnerability in Apollo Gateway allowed queries with deeply nested and reused named fragments to be prohibitively expensive to query plan, specifically during named fragment expansion. This could lead to excessive resource consumption and denial of service.
Details
Named fragments were being expanded once per fragment spread during query planning, leading to exponential resource usage when deeply nested and reused fragments were involved.
Fix/Mitigation
A new Query Fragment Expansion Limit metric has been introduced:
This metric computes the number of selections a query would have if its fragment spreads were fully expanded.
The metric is checked against a limit to prevent excessive computation.
Patches
This has been remediated in @apollo/gateway version 2.10.1.
Workarounds
No known direct workarounds exist.
References
Acknowledgements
We appreciate the efforts of the security community in identifying and improving the performance and security of query planning mechanisms.