In versions 14.1.0-14.1.0.1 and 14.1.2.5-14.1.2.7, when a BIG-IP object is created or listed through the REST interface, the protected fields are obfuscated in the REST response, not protected via a SecureVault cryptogram as TMSH does. One example of protected fields is the GTM monitor password.
References
| Link | Resource |
|---|---|
| https://support.f5.com/csp/article/K20059815 | Vendor Advisory |
| https://support.f5.com/csp/article/K20059815 | Vendor Advisory |
Configurations
Configuration 1 (hide)
|
History
21 Nov 2024, 05:34
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://support.f5.com/csp/article/K20059815 - Vendor Advisory |
Information
Published : 2020-11-05 20:15
Updated : 2024-11-21 05:34
NVD link : CVE-2020-5943
Mitre link : CVE-2020-5943
CVE.ORG link : CVE-2020-5943
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_ddos_hybrid_defender
- big-ip_domain_name_system
- big-ip_fraud_protection_service
- big-ip_link_controller
- big-ip_local_traffic_manager
- big-ip_advanced_web_application_firewall
- big-ip_advanced_firewall_manager
- big-ip_access_policy_manager
- big-ip_ssl_orchestrator
- big-ip_analytics
CWE
CWE-327
Use of a Broken or Risky Cryptographic Algorithm