SNMP vulnerability CVE-2019-6613

ID F5:K27400151
Type f5
Reporter f5
Modified 2019-05-06T20:23:00


F5 Product Development has assigned ID 691767 (BIG-IP) to this vulnerability. Additionally, BIG-IP iHealth may list Heuristic H27400151 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 | None | 14.0.0 | Medium | 5.3 | SNMP
13.x | 13.0.0 - 13.1.1 |
12.x | 12.1.0 - 12.1.4 |
11.x | 11.6.1 - 11.6.3
11.5.1 - 11.5.8 | 11.6.4
Enterprise Manager | 3.x | None | Not applicable | Not vulnerable | None | None
BIG-IQ Centralized Management | 6.x | None | Not applicable | Not vulnerable | None | None
5.x | None | Not applicable
F5 iWorkflow | 2.x | None | Not applicable | Not vulnerable | None | None
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.


To mitigate this vulnerability, you can implement SNMPv3 with secure AES-128 encryption. To do so, refer to K13625: Overview of SNMPv3 agent access.

Impact of action: Performing this action should not have a negative impact on your system.