F5 discloses six critical BIG-IP flaws that can crash TMM in specific configurations

F5 has disclosed six critical BIG-IP vulnerabilities that let an unauthenticated attacker crash the TMM and interrupt traffic. Each depends on a specific virtual server setup. The headline also mentions possible remote code execution.

A technician seen from behind walks down a server rack aisle in a data centre.

Key points

  • Six critical vulnerabilities affect F5 BIG-IP.
  • An attacker needs no login to crash the Traffic Management Microkernel (TMM).
  • Traffic is disrupted until the TMM restarts.
  • Each flaw requires a specific virtual server setup: an iRule using a particular command, or an APM policy with two particular agent types.
  • The source headline notes that remote code execution may be possible.

F5, the maker of BIG-IP, has disclosed six critical vulnerabilities in the product. According to the report, an attacker who has not logged in can use them to crash the Traffic Management Microkernel (TMM), the component that handles traffic. Traffic is disrupted until the TMM restarts.

Who is exposed

The flaws are not triggered on every deployment. Each one requires a specific configuration on a virtual server: either an iRule that uses a particular command, or an APM policy that includes two particular kinds of agent. The source headline also says the flaws may allow remote code execution, but the excerpt available to us does not give further detail on that point.

What this means for your organisation

BIG-IP often sits in front of critical services, so a TMM crash can interrupt availability for the applications behind it. The practical first step is to find out whether your virtual servers use the affected iRule or APM configurations, since that determines real exposure.

The excerpt does not list CVE identifiers, affected versions or fixes. Teams should take those details directly from the F5 advisory before planning changes.

What to do now

  1. Inventory all BIG-IP devices and identify which virtual servers use iRules or APM policies.
  2. Review those iRules and APM policies against the configuration conditions described in F5's advisory.
  3. Obtain CVE identifiers, affected versions and fixes from F5's official advisory and plan remediation accordingly.
  4. Prioritise internet-facing and business-critical virtual servers for review and patching.
  5. Confirm that availability monitoring and failover for BIG-IP would detect and handle a TMM restart, in line with your business continuity plans.

How useful was this story?

Need help acting on this?

Our consultants can assess your exposure and map the change to your controls and evidence.

Talk to an expert

Regulatory updates in your inbox

SAMA, NCA and SDAIA changes and what they mean for your institution — once a month.

E-mails in

We confirm by e-mail; unsubscribe any time. Manage your subscription · Past issues

Schedule a Free Assessment