TMM vulnerability CVE-2018-15319

ID F5:K64208870
Type f5
Reporter f5
Modified 2018-12-17T23:16:00


F5 Product Development has assigned ID 722091 (BIG-IP) to this vulnerability. Additionally, BIG-IP iHealth may list Heuristic H64208870 on the Diagnostics > Identified > High 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 | 14.0.0 | 14.1.0 | High | 7.5 | TMM
13.x | 13.0.0 - 13.1.1 |
12.x | 12.1.0 - 12.1.3 |
11.x | None | Not applicable
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
4.x | None | Not applicable
BIG-IQ Cloud and Orchestration | 1.x | None | Not applicable | Not vulnerable | None | None
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

1 The 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 should avoid using the following options:

  • The normalize option with L7 policies.
  • The -normalize option with HTTP::uri, HTTP::query, or HTTP::path iRules commands.

Impact of action: The impact of the suggested mitigation depends on the specific environment. F5 recommends that you test any such changes during a maintenance window and consider the possible impact on your specific environment.