F5 warns six critical BIG-IP flaws can crash traffic and may allow remote code execution
Only engineering hotfixes are offered for now, with no workaround, and F5 warns they lack the full testing of scheduled releases.
F5 has published six critical BIG-IP flaws, each rated 9.8 under CVSS v3.1, that let an unauthenticated attacker crash the Traffic Management Microkernel and disrupt traffic until it restarts, with possible remote code execution. Each flaw only applies under a particular configuration, such as a specific iRule command or an APM policy pairing two agent types. The only remedy listed is engineering hotfixes, which F5 says lack the full QA of scheduled releases and come with no warranty, and no workaround is offered. F5 has not reported any of these flaws as exploited, though it is a recurring target and one of its September APM flaws is already being used in attacks. Separately, lower-rated iControl REST and SOAP flaws, plus APM and SAML issues, are covered, with some fixed in scheduled releases and others only in hotfixes.
Why it matters
Operators running the affected BIG-IP configurations face a choice between applying hotfixes that have not gone through F5's full quality checks and leaving systems exposed to unauthenticated attacks that can halt traffic. Because F5 has no mitigation and no exploitation has been reported for these six flaws, the risk is concrete but not yet shown in attacks. The recent exploitation of an earlier APM flaw is a reminder that F5 devices are a recurring target, and that the scope of the danger depends on whether a given deployment uses one of the specific configurations involved.
Matters or hype?
Does this story matter, or is it hype? Vote before you see what everyone else said.