BIG-IP vulnerability CVE-2019-6688

ID F5:K25607522
Type f5
Reporter f5
Modified 2020-03-27T17:20:00


F5 Product Development has assigned ID 738236 (BIG-IP and BIG-IQ) 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.0.1 | 15.1.0 | Low | 3.1 | Password used for UCS backups
14.x | 14.1.0 - 14.1.2
14.0.0 - 14.0.1 |
13.x | 13.1.0 - 13.1.3 |
12.x | 12.1.0 - 12.1.5 |
11.x | 11.5.2 - 11.6.5 |
Enterprise Manager | 3.x | None | Not applicable | Not vulnerable2 | None | None
BIG-IQ Centralized Management | 7.x | None | 7.0.0 | Low | 3.1 | Password used for UCS backups
6.x | 6.0.0 - 6.1.0 | None
5.x | 5.2.0 - 5.4.0 | None
Traffix SDC | 5.x | None | Not applicable | Not vulnerable | None | 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.

2The specified products contain the affected code. However, F5 identifies the vulnerability status as Not vulnerable because the attacker cannot exploit the code in default, standard, or recommended configurations.

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.


To mitigate this vulnerability, you can disable all forms of user access by way of SNMP to the affected system, including the read-only access.