Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 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, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4
Fixed In:
15.1.0, 14.1.5, 13.1.3.2
Opened: Aug 09, 2019 Severity: 3-Major
A typical configuration of the HTTP Explicit Proxy includes four virtual servers: -- Two virtual servers for the Explicit Proxy, one IPv4, one IPv6. -- Two general-purpose virtual servers: one IPv4, one IPv6. The general-purpose virtual servers allow handling of CONNECT tunneling over the HTTP-tunnel interface. Unfortunately, if an IPv6 client tries to CONNECT to an IPv4 destination, it fails, returning a 503 status error. This is due to the IPv6 general-purpose virtual server not being found when performing the destination lookup.
The IPv6 client will not be able to "CONNECT" through the explicit proxy to an IPv4 address.
-- The HTTP explicit proxy virtual server is listening on an IPv6 address. -- 'default-connect-handling deny' is configured on the explicit proxy HTTP profile. -- IPv4 and IPv6 general-purpose virtual servers exist on the HTTP-tunnel interface. -- The client connects, and uses CONNECT to proxy to an IPv4 address.
None.
Mismatched IPv6 to IPv4 scenarios are supported with the HTTP Explicit Proxy.