DoS Wars: Revenge of the Fragments
summary
Fragments can hide exponential work behind linear execution: validation often visits named fragments once while some validators and planners do not, producing exponential validation or planning time and enabling denial‑of‑service. Examples include CVE-2025-31496 (Apollo compiler revisiting fragments), planner blowups in Apollo Router and Gateway from inlining fragments, and a wrapping arithmetic bug that lets metrics overflow. Remedies: memoize fragment visits, precompute expanded operation size, and use non‑wrapping integer types for cost limits.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:03Fragment cycles and execution
- 2:46Field collection in fragments
- 7:39Apollo compiler vulnerability
- 8:42Federation query planner issues
- 10:03Router plugin arithmetic flaw
- 11:08Q&A
related talks
20mColocating & Composing Data Dependencies with Fragments
16mMitigating Transient-Execution Attacks with CHERI Compartments
13mEvading and crashing anti-malware solutions via data collection overloading during...
46mThe Anatomy of Java Vulnerabilities
46mRethinking Architectures and Abstraction for a World Where Security Improvements Matter More than Performance Gains
58mBuilding antifragile systems using Secure by Design
18mFavorite DeFi Vulnerabilities
52mStructure aware fuzzing