Strix
26.1K

CVE-2017-6144

UnknownEPSS 0.60%

Last modified

CVE-2017-6144 is a vulnerability of currently unknown severity. In F5 BIG-IP PEM 12.1.0 through 12.1.2 when downloading the Type Allocation Code (TAC) database file via HTTPS, the server's certificate is not verified. Attackers in a privileged network position may be able to launch a man-in-the-middle attack against these connections. EPSS estimates a 0.60% chance of exploitation in the next 30 days.

Description

In F5 BIG-IP PEM 12.1.0 through 12.1.2 when downloading the Type Allocation Code (TAC) database file via HTTPS, the server's certificate is not verified. Attackers in a privileged network position may be able to launch a man-in-the-middle attack against these connections. TAC databases are used in BIG-IP PEM for Device Type and OS (DTOS) and Tethering detection. Customers not using BIG-IP PEM, not configuring downloads of TAC database files, or not using HTTP for that download are not affected.

Metrics

EPSS Probability
0.60%

44.1th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
F5Big-Ip Policy Enforcement Manager12.1.0
F5Big-Ip Policy Enforcement Manager12.1.1
F5Big-Ip Policy Enforcement Manager12.1.2

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2017-6144?
In F5 BIG-IP PEM 12.1.0 through 12.1.2 when downloading the Type Allocation Code (TAC) database file via HTTPS, the server's certificate is not verified. Attackers in a privileged network position may be able to launch a man-in-the-middle attack against these connections. TAC databases are used in BIG-IP PEM for Device Type and OS (DTOS) and Tethering detection. Customers not using BIG-IP PEM, not configuring downloads of TAC database files, or not using HTTP for that download are not affected.
How severe is CVE-2017-6144?
Severity scoring for CVE-2017-6144 is pending analysis. The EPSS model estimates a 0.60% probability of exploitation in the next 30 days.
How do I fix CVE-2017-6144?
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.

How Strix Helps

Related CVEs from 2017

View all 2017CVEs →

Are you affected by CVE-2017-6144?

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

Scan your code now

Source: NVD / NIST