TMM vulnerability CVE-2019-6660

2019-11-14T22:00:00
ID F5:K23860356
Type f5
Reporter f5
Modified 2020-01-08T10:16:00

Description

F5 Product Development has assigned ID 767653 (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 | None | 15.0.0 | High | 7.5 | TMM
14.x | 14.1.0 - 14.1.2
14.0.0 - 14.0.1 | 14.1.2.1
14.0.1.1
13.x | 13.1.0 - 13.1.1 | 13.1.3
12.x | None | Not applicable
11.x | None | Not applicable
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 | 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 modify any iRule that performs HTTP header manipulation on the affected virtual server, to stop processing when the system detects an HTTP request that uses version HTTP/0.9.

An example of an iRules statement that detects and stops the processing of an HTTP request that uses version HTTP/0.9 may appear as follows:
if {[HTTP::version] equals "0.9"} {return}

For the mitigation to be effective, you have to:

  1. Use the iRules statement in existing iRules that preform HTTP header manipulation.
  2. Insert the iRules statement at the top of HTTP iRule events.

You can insert the statement into an existing iRule that handles HTTP requests for the affected virtual server.

For example, take the following rule:

ltm rule /Common/My_Existing_iRule {
when HTTP_REQUEST {

<Existing iRule statements>

}
}

Insert the statement if {[HTTP::version] equals "0.9"} {return} at the top of the HTTP event:

ltm rule /Common/My_Existing_iRule {
when HTTP_REQUEST {
if {[HTTP::version] equals "0.9"} {return}

<Existing iRule statements>

}
}