F5 iRules vulnerability CVE-2019-6685

2019-12-20T22:37:00
ID F5:K30215839
Type f5
Reporter f5
Modified 2020-03-27T17:18:00

Description

F5 Product Development has assigned ID 782529 (BIG-IP) 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
15.0.1.3 | Medium | 6.7 | iRules
14.x | 14.1.0 - 14.1.2
14.0.0 - 14.0.1 | 14.1.2.3
14.0.1.1
13.x | 13.1.0 - 13.1.3 | 13.1.3.2
12.x | 12.1.0 - 12.1.5 | 12.1.5.1
11.x | 11.5.2 - 11.6.5 | 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
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.

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.

Mitigation

To mitigate this vulnerability, you can reduce the privileges of roles such as iRules Manager because more highly privileged roles, such as the Resource Administrator role, already have access privileges. If possible, remove the iRules Manager role from use to mitigate the attack.