CVE-2017-6150

UnknownEPSS 1.84%

Last modified

CVE-2017-6150 is a vulnerability of currently unknown severity. Under certain conditions for F5 BIG-IP systems 13.0.0 or 12.1.0 - 12.1.3.1, using FastL4 profiles, when the Reassemble IP Fragments option is disabled (default), some specific large fragmented packets may restart the Traffic Management Microkernel (TMM).. EPSS estimates a 1.84% chance of exploitation in the next 30 days.

Description

Under certain conditions for F5 BIG-IP systems 13.0.0 or 12.1.0 - 12.1.3.1, using FastL4 profiles, when the Reassemble IP Fragments option is disabled (default), some specific large fragmented packets may restart the Traffic Management Microkernel (TMM).

Metrics

EPSS Probability
1.84%

76.2th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
F5Big-Ip Local Traffic Manager>= 12.1.0, <= 12.1.3.1
F5Big-Ip Local Traffic Manager13.0.0
F5Big-Ip Application Acceleration Manager>= 12.1.0, <= 12.1.3.1
F5Big-Ip Application Acceleration Manager13.0.0
F5Big-Ip Advanced Firewall Manager>= 12.1.0, <= 12.1.3.1
F5Big-Ip Advanced Firewall Manager13.0.0
F5Big-Ip Analytics>= 12.1.0, <= 12.1.3.1
F5Big-Ip Analytics13.0.0
F5Big-Ip Access Policy Manager>= 12.1.0, <= 12.1.3.1
F5Big-Ip Access Policy Manager13.0.0
F5Big-Ip Application Security Manager>= 12.1.0, <= 12.1.3.1
F5Big-Ip Application Security Manager13.0.0
F5Big-Ip Dns>= 12.1.0, <= 12.1.3.1
F5Big-Ip Dns13.0.0
F5Big-Ip Link Controller>= 12.1.0, <= 12.1.3.1
F5Big-Ip Link Controller13.0.0
F5Big-Ip Policy Enforcement Manager>= 12.1.0, <= 12.1.3.1
F5Big-Ip Policy Enforcement Manager13.0.0
F5Big-Ip Websafe>= 12.1.0, <= 12.1.3.1
F5Big-Ip Websafe13.0.0

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2017-6150?
Under certain conditions for F5 BIG-IP systems 13.0.0 or 12.1.0 - 12.1.3.1, using FastL4 profiles, when the Reassemble IP Fragments option is disabled (default), some specific large fragmented packets may restart the Traffic Management Microkernel (TMM).
How severe is CVE-2017-6150?
Severity scoring for CVE-2017-6150 is pending analysis. The EPSS model estimates a 1.84% probability of exploitation in the next 30 days.
How do I fix CVE-2017-6150?
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-6150?

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

Scan your code now

Source: NVD / NIST