F5 has released engineering hotfixes for several critical flaws in BIG-IP, The Hacker News reports. The company disclosed six issues that can disrupt traffic on the data plane, and it says they may also allow remote code execution in some cases. F5 has not reported that the flaws have been exploited. There is no listed workaround. The fixes are engineering hotfixes, meaning builds issued between regular software releases, and F5 notes that those builds do not go through the same QA process as a scheduled release. Some related BIG-IP Next for Kubernetes and BIG-IP CNF versions have their own hotfix builds.
If you operate BIG-IP, or the related Kubernetes and cloud-native editions F5 named, install the matching hotfix now. I am not going to walk through trigger conditions or exploit details here. Get the builds from F5 and apply them.
My take
A critical data-plane bug on a traffic box is not something to leave for the next quarterly window, even if the fix arrives as an engineering hotfix. Confirm you are on the build F5 assigned to your branch, and do not assume a later scheduled release already contains the fix until F5 says it does.
God Bless, and May the Source Be with You!