cve.bz

CVE-2016-5736 f5: Improper Access Control

7.5 highEPSS 2.3%

High (7.5) in f5. EPSS 2.3% estimated probability of exploitation activity in the next 30 days.

On this page
The default configuration of the IPsec IKE peer listener in F5 BIG-IP LTM, Analytics, APM, ASM, and Link Controller 11.2.1 before HF16, 11.4.x, 11.5.x before 11.5.4 HF2, 11.6.x before 11.6.1, and 12.x before 12.0.0 HF2; BIG-IP AAM, AFM, and PEM 11.4.x, 11.5.x before 11.5.4 HF2, 11.6.x before 11.6.1, and 12.x before 12.0.0 HF2; BIG-IP DNS 12.x before 12.0.0 HF2; BIG-IP Edge Gateway, WebAccelerator, and WOM 11.2.1 before HF16; BIG-IP GTM 11.2.1 before HF16, 11.4.x, 11.5.x before 11.5.4 HF2, and 11.6.x before 11.6.1; and BIG-IP PSM 11.4.0 through 11.4.1 improperly enables the anonymous IPsec IKE peer configuration object, which allows remote attackers to establish an IKE Phase 1 negotiation and possibly conduct brute-force attacks against Phase 2 negotiations via unspecified vectors.

Severity

CVSS 3.0

7.5 high
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
2.3% (unchanged from 2.3% a week ago; 2.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 83rd percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-284 Improper Access Control
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2016-5736 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2016-5736?via=ask-ai-copy and https://cve.bz/cve/CVE-2016-5736?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2016-5736 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
f5:big-ip_application_acceleration_manager11.4.0
f5:big-ip_application_acceleration_manager11.4.1
f5:big-ip_application_acceleration_manager11.5.0
f5:big-ip_application_acceleration_manager11.5.1
f5:big-ip_application_acceleration_manager11.5.2
f5:big-ip_application_acceleration_manager11.5.3
f5:big-ip_application_acceleration_manager11.5.4
f5:big-ip_application_acceleration_manager11.6.0
f5:big-ip_application_acceleration_manager12.0.0
f5:big-ip_webaccelerator11.2.1
f5:big-ip_analytics11.2.1
f5:big-ip_analytics11.4.0
f5:big-ip_analytics11.4.1
f5:big-ip_analytics11.5.0
f5:big-ip_analytics11.5.1
f5:big-ip_analytics11.5.2
f5:big-ip_analytics11.5.3
f5:big-ip_analytics11.5.4
f5:big-ip_analytics11.6.0
f5:big-ip_analytics12.0.0
f5:big-ip_domain_name_system12.0.0
f5:big-ip_edge_gateway11.2.1
f5:big-ip_access_policy_manager11.2.1
f5:big-ip_access_policy_manager11.4.0
f5:big-ip_access_policy_manager11.4.1
f5:big-ip_access_policy_manager11.5.0
f5:big-ip_access_policy_manager11.5.1
f5:big-ip_access_policy_manager11.5.2
f5:big-ip_access_policy_manager11.5.3
f5:big-ip_access_policy_manager11.5.4
f5:big-ip_access_policy_manager11.6.0
f5:big-ip_access_policy_manager12.0.0
f5:big-ip_local_traffic_manager11.2.1
f5:big-ip_local_traffic_manager11.4.0
f5:big-ip_local_traffic_manager11.4.1
f5:big-ip_local_traffic_manager11.5.0
f5:big-ip_local_traffic_manager11.5.1
f5:big-ip_local_traffic_manager11.5.2
f5:big-ip_local_traffic_manager11.5.3
f5:big-ip_local_traffic_manager11.5.4
f5:big-ip_local_traffic_manager11.6.0
f5:big-ip_local_traffic_manager12.0.0
f5:big-ip_advanced_firewall_manager11.4.0
f5:big-ip_advanced_firewall_manager11.4.1
f5:big-ip_advanced_firewall_manager11.5.0
f5:big-ip_advanced_firewall_manager11.5.1
f5:big-ip_advanced_firewall_manager11.5.2
f5:big-ip_advanced_firewall_manager11.5.3
f5:big-ip_advanced_firewall_manager11.5.4
f5:big-ip_advanced_firewall_manager11.6.0
f5:big-ip_advanced_firewall_manager12.0.0
f5:big-ip_websafe11.6.0
f5:big-ip_websafe12.0.0
f5:big-ip_policy_enforcement_manager11.4.0
f5:big-ip_policy_enforcement_manager11.4.1
f5:big-ip_policy_enforcement_manager11.5.0
f5:big-ip_policy_enforcement_manager11.5.1
f5:big-ip_policy_enforcement_manager11.5.2
f5:big-ip_policy_enforcement_manager11.5.3
f5:big-ip_policy_enforcement_manager11.5.4
f5:big-ip_policy_enforcement_manager11.6.0
f5:big-ip_policy_enforcement_manager12.0.0
f5:big-ip_global_traffic_manager11.2.1
f5:big-ip_global_traffic_manager11.4.0
f5:big-ip_global_traffic_manager11.4.1
f5:big-ip_global_traffic_manager11.5.0
f5:big-ip_global_traffic_manager11.5.1
f5:big-ip_global_traffic_manager11.5.2
f5:big-ip_global_traffic_manager11.5.3
f5:big-ip_global_traffic_manager11.5.4
f5:big-ip_global_traffic_manager11.6.0
f5:big-ip_link_controller11.2.1
f5:big-ip_link_controller11.4.0
f5:big-ip_link_controller11.4.1
f5:big-ip_link_controller11.5.0
f5:big-ip_link_controller11.5.1
f5:big-ip_link_controller11.5.2
f5:big-ip_link_controller11.5.3
f5:big-ip_link_controller11.5.4
f5:big-ip_link_controller11.6.0
f5:big-ip_link_controller12.0.0
f5:big-ip_protocol_security_module11.4.0
f5:big-ip_protocol_security_module11.4.1
f5:big-ip_wan_optimization_manager11.2.1
f5:big-ip_application_security_manager11.2.1
f5:big-ip_application_security_manager11.4.0
f5:big-ip_application_security_manager11.4.1
f5:big-ip_application_security_manager11.5.0
f5:big-ip_application_security_manager11.5.1
f5:big-ip_application_security_manager11.5.2
f5:big-ip_application_security_manager11.5.3
f5:big-ip_application_security_manager11.5.4
f5:big-ip_application_security_manager11.6.0
f5:big-ip_application_security_manager12.0.0

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-284 (17).

References

Check your stackJSON