First published: Tue Jan 10 2017(Updated: )
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.
Credit: f5sirt@f5.com
Affected Software | Affected Version | How to fix |
---|---|---|
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.0 | |
F5 Big-ip Websafe | =12.1.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.