Fastly Next-Gen WAF Agent: Fail-Open During Kubernetes Pod Startup
In a default Kubernetes deployment of the Fastly Next-Gen WAF (formerly Signal Sciences) with the NGINX module and a sigsci-agent sidecar, a new pod can accept and forward traffic before the agent has loaded its rules. Until the agent opens its socket, the module fails open. Once the socket exists but no ruleset has loaded, the agent answers every request with “allow.” It stays that way for as long as the configuration cannot be loaded, while the pod reports Ready. This post covers the mechanism, lab test results on the current agent, how to check your own deployment, the opt-in mitigation Fastly shipped, and the CVE submission. The story of how I found it is in my April 12 post. ...