F5 Product Development has assigned ID 708653 (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 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 | Not applicable | Low | 3.7 | LRO feature |
13.x | 13.0.0 - 13.1.0 | 13.1.0.6 | ||||
12.x | 12.1.0 - 12.1.3 | 12.1.3.6 | ||||
11.x | 11.6.0 - 11.6.3 | 11.6.3.3 | ||||
11.5.1 - 11.5.6 | 11.5.7 | |||||
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 theFixes 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 disable LRO by modifying the tm.tcplargereceiveoffload database variable. To do so, perform the following procedure:
Impact of procedure: The following procedure restarts the Traffic Management Microkernel (TMM), and you should perform the procedure only during a maintenance window. Disabling LRO may increase CPU usage.
tmsh
modify /sys db tm.tcplargereceiveoffload value disable
restart /sys service tmm