Strix
26.1K

CVE-2016-5700

UnknownEPSS 6.42%

Last modified

CVE-2016-5700 is a vulnerability of currently unknown severity. Virtual servers in F5 BIG-IP systems 11.5.0, 11.5.1 before HF11, 11.5.2, 11.5.3, 11.5.4 before HF2, 11.6.0 before HF8, 11.6.1 before HF1, 12.0.0 before HF4, and 12.1.0 before HF2, when configured with the HTTP Explicit Proxy functionality or SOCKS profile, allow remote attackers to modify the system configuration, read system files, and possibly execute arbitrary code via unspecified vectors.. EPSS estimates a 6.42% chance of exploitation in the next 30 days.

Description

Virtual servers in F5 BIG-IP systems 11.5.0, 11.5.1 before HF11, 11.5.2, 11.5.3, 11.5.4 before HF2, 11.6.0 before HF8, 11.6.1 before HF1, 12.0.0 before HF4, and 12.1.0 before HF2, when configured with the HTTP Explicit Proxy functionality or SOCKS profile, allow remote attackers to modify the system configuration, read system files, and possibly execute arbitrary code via unspecified vectors.

Metrics

EPSS Probability
6.42%

92.8th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
F5Big-Ip Policy Enforcement Manager11.5.0
F5Big-Ip Policy Enforcement Manager11.5.1
F5Big-Ip Policy Enforcement Manager11.5.2
F5Big-Ip Policy Enforcement Manager11.5.3
F5Big-Ip Policy Enforcement Manager11.5.4
F5Big-Ip Policy Enforcement Manager11.6.0
F5Big-Ip Policy Enforcement Manager11.6.1
F5Big-Ip Policy Enforcement Manager12.0.0
F5Big-Ip Policy Enforcement Manager12.1.0
F5Big-Ip Local Traffic Manager11.5.0
F5Big-Ip Local Traffic Manager11.5.1
F5Big-Ip Local Traffic Manager11.5.2
F5Big-Ip Local Traffic Manager11.5.3
F5Big-Ip Local Traffic Manager11.5.4
F5Big-Ip Local Traffic Manager11.6.0
F5Big-Ip Local Traffic Manager11.6.1
F5Big-Ip Local Traffic Manager12.0.0
F5Big-Ip Local Traffic Manager12.1.0
F5Big-Ip Websafe11.6.0
F5Big-Ip Websafe11.6.1
F5Big-Ip Websafe12.0.0
F5Big-Ip Websafe12.1.0
F5Big-Ip Link Controller11.5.0
F5Big-Ip Link Controller11.5.1
F5Big-Ip Link Controller11.5.2
F5Big-Ip Link Controller11.5.3
F5Big-Ip Link Controller11.5.4
F5Big-Ip Link Controller11.6.0
F5Big-Ip Link Controller11.6.1
F5Big-Ip Link Controller12.0.0
F5Big-Ip Link Controller12.1.0
F5Big-Ip Application Acceleration Manager11.5.0
F5Big-Ip Application Acceleration Manager11.5.1
F5Big-Ip Application Acceleration Manager11.5.2
F5Big-Ip Application Acceleration Manager11.5.3
F5Big-Ip Application Acceleration Manager11.5.4
F5Big-Ip Application Acceleration Manager11.6.0
F5Big-Ip Application Acceleration Manager11.6.1
F5Big-Ip Application Acceleration Manager12.0.0
F5Big-Ip Application Acceleration Manager12.1.0
F5Big-Ip Access Policy Manager11.5.0
F5Big-Ip Access Policy Manager11.5.1
F5Big-Ip Access Policy Manager11.5.2
F5Big-Ip Access Policy Manager11.5.3
F5Big-Ip Access Policy Manager11.5.4
F5Big-Ip Access Policy Manager11.6.0
F5Big-Ip Access Policy Manager11.6.1
F5Big-Ip Access Policy Manager12.0.0
F5Big-Ip Access Policy Manager12.1.0
F5Big-Ip Advanced Firewall Manager11.5.0

Showing 50 of 67 affected configurations. See NVD for the full list.

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2016-5700?
Virtual servers in F5 BIG-IP systems 11.5.0, 11.5.1 before HF11, 11.5.2, 11.5.3, 11.5.4 before HF2, 11.6.0 before HF8, 11.6.1 before HF1, 12.0.0 before HF4, and 12.1.0 before HF2, when configured with the HTTP Explicit Proxy functionality or SOCKS profile, allow remote attackers to modify the system configuration, read system files, and possibly execute arbitrary code via unspecified vectors.
How severe is CVE-2016-5700?
Severity scoring for CVE-2016-5700 is pending analysis. The EPSS model estimates a 6.42% probability of exploitation in the next 30 days.
How do I fix CVE-2016-5700?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2016-5700?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST