F5 Product Development has assigned ID 746091 (BIG-IP), ID 709043 (BIG-IQ), and ID 345678 (Enterprise Manager) to this vulnerability.
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, point 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) | 15.x | 15.0.0 - 15.1.0 | None | Low | 3.1 | tmsh
14.x | 14.0.0 - 14.1.2 | None
13.x | 13.0.0 - 13.1.3 | None
12.x | 12.1.0 - 12.1.5 | None
11.x | 11.5.1 - 11.6.5 | None
Enterprise Manager | 3.x | 3.1.1 | None | Low | 3.1 | tmsh
BIG-IQ Centralized Management | 7.x | 7.0.0 | None | Low | 3.1 | tmsh
6.x | 6.0.0 - 6.1.0 | None
5.x | 5.0.0 - 5.4.0 | None
F5 iWorkflow | 2.x | 2.3.0 | None | Low | 3.1 | tmsh
Traffix SDC | 5.x | None | Not applicable | Not vulnerable | None | None
4.x | None | Not applicable
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 this vulnerability. However, administrative users that have only Configuration utility permissions cannot exploit this vulnerability.
F5 would like to acknowledge Rich Mirch for bringing this issue to our attention and following the highest standards of responsible disclosure.