Under certain conditions for BIG-IP systems using a virtual server with an associated FastL4 profile and TCP analytics profile, a specific sequence of packets may cause the Traffic Management Microkernel (TMM) to restart.
| Vulnerable Product | Search on Vulmon | Subscribe to Product |
|---|---|---|
f5 big-ip local traffic manager 12.1.0 |
||
f5 big-ip local traffic manager 12.1.1 |
||
f5 big-ip application acceleration manager 12.1.0 |
||
f5 big-ip application acceleration manager 12.1.1 |
||
f5 big-ip advanced firewall manager 12.1.0 |
||
f5 big-ip advanced firewall manager 12.1.1 |
||
f5 big-ip analytics 12.1.0 |
||
f5 big-ip analytics 12.1.1 |
||
f5 big-ip access policy manager 12.1.0 |
||
f5 big-ip access policy manager 12.1.1 |
||
f5 big-ip application security manager 12.1.0 |
||
f5 big-ip application security manager 12.1.1 |
||
f5 big-ip domain name system 12.1.0 |
||
f5 big-ip domain name system 12.1.1 |
||
f5 big-ip link controller 12.1.0 |
||
f5 big-ip link controller 12.1.1 |
||
f5 big-ip policy enforcement manager 12.1.0 |
||
f5 big-ip policy enforcement manager 12.1.1 |
||
f5 big-ip websafe 12.1.1 |
||
f5 big-ip websafe 12.1.0 |
Vulmon