OpenSSL vulnerability CVE-2019-1547

ID F5:K73422160
Type f5
Reporter f5
Modified 2019-10-10T03:43:00


F5 Product Development has assigned CPF-25136 and CPF-25137 (Traffix) 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 | None | Not applicable | Not vulnerable | None | None
14.x | None | Not applicable
13.x | None | Not applicable
12.x | None | Not applicable
11.x | None | Not applicable
BIG-IP (APM Clients) | 7.1.x | None | Not applicable | Not vulnerable2 | None | None
Enterprise Manager | 3.x | None | Not applicable | Not vulnerable | None | None
BIG-IQ Centralized Management | 7.x | None | Not applicable | Not vulnerable | None | None
6.x | None | Not applicable
5.x | None | Not applicable
F5 iWorkflow | 2.x | None | Not applicable | Not vulnerable | None | None
Traffix SDC | 5.x | 5.0.0 - 5.1.0 | None | Medium | 5.5 | OpenSSL

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.