Last Modified: Apr 11, 2024
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 17.0.0, 17.0.0.1, 17.0.0.2
Fixed In:
17.1.0, 16.1.4, 15.1.9
Opened: Dec 23, 2021 Severity: 3-Major
Traffic is supposed to be routed to virtual servers based on which ever one has the best (i.e. most specific) match to the incoming traffic using destination address/port and source address (see https://support.f5.com/csp/article/K14800). But this does not always work correctly, e.g. when two virtual servers use destination port any.
Traffic is routed to the wrong virtual server.
Here's an example where this is a problem: 1) Two virtual servers with the same destination address both using port any. 2) One server uses a wildcard source address and one a specific address. For instance: ltm virtual test1 { destination 10.93.19.5:any ip-protocol tcp mask 255.255.255.255 pool pool1 profiles { tcp { } } serverssl-use-sni disabled source 0.0.0.0/0 source-address-translation { type automap } translate-address enabled translate-port disabled vs-index 2 } ltm virtual test2 { destination 10.93.19.5:any ip-protocol tcp mask 255.255.255.255 pool pool1 profiles { tcp { } } serverssl-use-sni disabled source 10.93.19.2/32 source-address-translation { type automap } translate-address enabled translate-port disabled vs-index 3 } Traffic from 10.93.19.2 will be incorrectly routed to the test1 server.
Avoid multiple virtual servers with the same destination address and port any.
N/A