F5 Product Development has assigned ID 757604 (BIG-IP), ID 757604-8 (BIG-IQ), ID 757604-9 (Enterprise Manager), ID 757604-10 (F5 iWorkflow), and CPF-25054 and CPF-25055 (Traffix) to this vulnerability. Additionally, BIG-IP iHealth may list Heuristic H11315080 on the Diagnostics > Identified > Medium page.
To determine if your product and version have been evaluated for this vulnerability, refer to the Applies to (see versions) box. To determine if your release is known to be vulnerable, the components or features that are affected by the vulnerability, and for information about releases or hotfixes that address the vulnerability, refer to the following table. For more information about security advisory versioning, refer to K51812227: Understanding Security Advisory versioning.
Product | Branch | Versions known to be vulnerable | Fixes introduced in | Severity | CVSSv3 score1 | Vulnerable component or feature
BIG-IP (LTM, AAM, AFM, Analytics, APM, ASM, DNS, Edge Gateway, FPS, GTM, Link Controller, PEM, WebAccelerator) | 14.x | 14.0.0 - 14.1.0 | None | Medium | 5.3 | OpenSSH (SCP client)
13.x | 13.0.0 - 13.1.1 | None
12.x | 12.1.0 - 12.1.4 | None
11.x | 11.5.1 - 11.6.3 | None
Enterprise Manager | 3.x | 3.1.1 | None | Medium | 5.3 | OpenSSH (SCP client)
BIG-IQ Centralized Management | 6.x | 6.0.0 - 6.1.0 | None | Medium | 5.3 | OpenSSH (SCP client)
5.x | 5.0.0 - 5.4.0 | None
F5 iWorkflow | 2.x | 2.3.0 | None | Medium | 5.3 | OpenSSH (SCP client)
Traffix SDC | 5.x | 5.0.0 - 5.1.0 | None | Medium | 5.3 | OpenSSH (SCP client)
4.x | 4.4.0 | None
1The CVSSv3 score link takes you to a resource outside of AskF5, and it is possible that the document may be removed without our knowledge.
If you are running a version listed in the Versions known to be vulnerable column, you can eliminate this vulnerability by upgrading to a version listed in the Fixes introduced in column. If the table lists only an older version than what you are currently running, or does not list a non-vulnerable version, then no upgrade candidate currently exists.
There is no mitigation for a man-in-the-middle (MITM) attack.
You can mitigate the vulnerability from a malicious server by verifying the host key fingerprint when connecting to systems with the SCP client.