CVE-2017-0301

UnknownEPSS 0.53%

Last modified

CVE-2017-0301 is a vulnerability of currently unknown severity. In F5 BIG-IP APM software versions 11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.6.0, 11.6.1, 12.0.0, 12.1.0, 12.1.1 and 12.1.2 BIG-IP APM portal access requests do not return the intended resources in some cases. This may allow access to internal BIG-IP APM resources, however the application resources and backend servers are unaffected.. EPSS estimates a 0.53% chance of exploitation in the next 30 days.

Description

In F5 BIG-IP APM software versions 11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.6.0, 11.6.1, 12.0.0, 12.1.0, 12.1.1 and 12.1.2 BIG-IP APM portal access requests do not return the intended resources in some cases. This may allow access to internal BIG-IP APM resources, however the application resources and backend servers are unaffected.

Metrics

EPSS Probability
0.53%

41.0th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

VendorProductVersions
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 Access Policy Manager12.1.1
F5Big-Ip Access Policy Manager12.1.2

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2017-0301?
In F5 BIG-IP APM software versions 11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.6.0, 11.6.1, 12.0.0, 12.1.0, 12.1.1 and 12.1.2 BIG-IP APM portal access requests do not return the intended resources in some cases. This may allow access to internal BIG-IP APM resources, however the application resources and backend servers are unaffected.
How severe is CVE-2017-0301?
Severity scoring for CVE-2017-0301 is pending analysis. The EPSS model estimates a 0.53% probability of exploitation in the next 30 days.
How do I fix CVE-2017-0301?
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-2017-0301?

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

Scan your code now

Source: NVD / NIST