F5 disclosed six critical flaws in BIG-IP that let an attacker, without logging in, crash the TMM traffic management microkernel and disrupt traffic until it restarts. The company says they may also allow remote code execution. Each requires a specific setup on a virtual server: five in iRules and one in the APM module. The management side is not exposed, and the company has not reported exploitation.
The fixes are engineering hotfixes only, interim builds that F5 says do not go through full QA, and there is no workaround until they are installed. Some of the flaws also affect BIG-IP Next for Kubernetes and BIG-IP CNF. F5 published 16 more advisories at the same time, including 10 for NGINX. Organizations running BIG-IP should check whether their configuration is affected and install the hotfix.