Plan ahead Medium Check your exposure
Six serious F5 BIG-IP flaws can crash traffic handling
The Hacker NewsF5, BIG-IP
What happened. F5 disclosed six critical flaws in BIG-IP. An attacker without a login can crash the Traffic Management Microkernel (TMM) and disrupt traffic until it restarts. Each flaw needs a specific setup, such as an iRule using a particular command or an APM policy with two kinds of agent.
Who is affected. Users of F5 BIG-IP. Industrial sites using it as a gateway for remote access are exposed, because vendors and engineers often reach plant systems through it.
What to do. Check whether your F5 BIG-IP virtual servers use the affected iRule command or APM policy agents, and apply F5's fixes and guidance.
When to act. Plan ahead: Check whether BIG-IP sits between office IT and plant networks before the next maintenance window.
Editor's reading
Forasset ownerOT security leadIT security
- Purdue level
- L5
- L3.5
Why: BIG-IP is a traffic and access gateway at the network boundary, so it sits in the industrial DMZ (L3.5) or at the internet edge (L5).
- Are you exposed?
Review your BIG-IP virtual server configurations for iRules using the named command and APM policies with the two named agent types.
- If you cannot fix it yet
- Limit which networks can reach the affected BIG-IP virtual servers.
- Remove or disable iRules and APM policy agents that match F5's affected configurations if not needed.
- Keep the gateway off the plant network until patched.
- Watch for
- Repeated TMM restarts or sudden drops in BIG-IP traffic.
- Unexpected requests to virtual servers that use the affected iRules or APM policies.
- ATT&CK for ICS
- T0814Denial of Service
Inferred from the facts above, not stated by the source. Check it against your own site before acting.
Source: The Hacker News (opens thehackernews.com)
Published by Industrial Cyber Brief · Editor: Abhinav Roy · Drafted by AI and checked by code: how this is made · Corrections
More on F5