First published: Thu Nov 05 2020(Updated: )
On BIG-IP versions 16.0.0-16.0.0.1 and 15.1.0-15.1.0.5, using the RESOLV::lookup command within an iRule may cause the Traffic Management Microkernel (TMM) to generate a core file and restart. This issue occurs when data exceeding the maximum limit of a hostname passes to the RESOLV::lookup command.
Credit: f5sirt@f5.com
Affected Software | Affected Version | How to fix |
---|---|---|
F5 BIG-IP Access Policy Manager | >=15.1.0<15.1.1 | |
F5 BIG-IP Access Policy Manager | >=16.0.0<16.0.1 | |
F5 BIG-IP Advanced Firewall Manager | >=15.1.0<15.1.1 | |
F5 BIG-IP Advanced Firewall Manager | >=16.0.0<16.0.1 | |
F5 BIG-IP Analytics | >=15.1.0<15.1.1 | |
F5 BIG-IP Analytics | >=16.0.0<16.0.1 | |
F5 Big-ip Application Acceleration Manager | >=15.1.0<15.1.1 | |
F5 Big-ip Application Acceleration Manager | >=16.0.0<16.0.1 | |
F5 BIG-IP Application Security Manager | >=15.1.0<15.1.1 | |
F5 BIG-IP Application Security Manager | >=16.0.0<16.0.1 | |
F5 Big-ip Domain Name System | >=15.1.0<15.1.1 | |
F5 Big-ip Domain Name System | >=16.0.0<16.0.1 | |
F5 Big-ip Fraud Protection Service | >=15.1.0<15.1.1 | |
F5 Big-ip Fraud Protection Service | >=16.0.0<16.0.1 | |
F5 Big-ip Global Traffic Manager | >=15.1.0<15.1.1 | |
F5 Big-ip Global Traffic Manager | >=16.0.0<16.0.1 | |
F5 Big-ip Link Controller | >=15.1.0<15.1.1 | |
F5 Big-ip Link Controller | >=16.0.0<16.0.1 | |
F5 Big-ip Local Traffic Manager | >=15.1.0<15.1.1 | |
F5 Big-ip Local Traffic Manager | >=16.0.0<16.0.1 | |
F5 Big-ip Policy Enforcement Manager | >=15.1.0<15.1.1 | |
F5 Big-ip Policy Enforcement Manager | >=16.0.0<16.0.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.