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.
References
Link | Resource |
---|---|
https://support.f5.com/csp/article/K03125360 | Vendor Advisory |
https://support.f5.com/csp/article/K03125360 | Vendor Advisory |
Configurations
Configuration 1 (hide)
|
History
21 Nov 2024, 05:34
Type | Values Removed | Values Added |
---|---|---|
References | () https://support.f5.com/csp/article/K03125360 - Vendor Advisory |
Information
Published : 2020-11-05 20:15
Updated : 2024-11-21 05:34
NVD link : CVE-2020-5941
Mitre link : CVE-2020-5941
CVE.ORG link : CVE-2020-5941
JSON object : View
Products Affected
f5
- big-ip_application_security_manager
- big-ip_application_acceleration_manager
- big-ip_global_traffic_manager
- big-ip_policy_enforcement_manager
- big-ip_domain_name_system
- big-ip_fraud_protection_service
- big-ip_link_controller
- big-ip_local_traffic_manager
- big-ip_advanced_firewall_manager
- big-ip_access_policy_manager
- big-ip_analytics
CWE