CVE-2020-5941: High severity f5 access policy manager vulnerability

Published Nov 5, 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.

Affected Software

22 affected components
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

Event History

Nov 5, 2020
CVE Published
via MITRE·07:18 PM
Data Sourced
via MITRE·07:18 PM
DescriptionWeakness

Frequently Asked Questions

1

What versions of F5 BIG-IP are affected by CVE-2020-5941?

F5 BIG-IP versions 16.0.0-16.0.0.1 and 15.1.0-15.1.0.5 are affected by CVE-2020-5941.

2

What is the impact of CVE-2020-5941?

CVE-2020-5941 may cause the Traffic Management Microkernel (TMM) to generate a core file and restart.

3

How can CVE-2020-5941 be mitigated?

To mitigate CVE-2020-5941, avoid using data exceeding the maximum limit of a hostname in the RESOLV::lookup command within an iRule.

4

Is a fix available for CVE-2020-5941?

Yes, a fix for CVE-2020-5941 can be found in the subsequent releases following the affected versions.

5

What command triggers the vulnerability in CVE-2020-5941?

The RESOLV::lookup command triggers the vulnerability in CVE-2020-5941 when used with excessive hostname data.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203