Last Modified: Jan 21, 2025
Affected Product(s):
BIG-IP APM
Known Affected Versions:
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, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6, 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, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1
Opened: Jan 16, 2025 Severity: 3-Major
If you define multiple Application Tunnels using IP:port (say 192.168.1.1:10000, 192.168.1.1:10001, etc.) and they are matching (on purpose) a wider layered virtual defined with a port range (say 192.168.1.1:10000-10100), then all your Application Tunnels will be hitting that virtual server with same destination first port only.
Application Tunnel will not establish with the appropriate port on the backend server.
- Multiple Application Tunnels are defined with same IP but different ports - Application Tunnels IP:port are matching a layered virtual configured with same IP and a port range containing the Application Tunnels defined ports
You must define a layered virtual server per Application Tunnel IP:port
None