Last Modified: Apr 24, 2024
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 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, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6, 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, 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, 17.0.0, 17.0.0.1, 17.0.0.2
Fixed In:
17.1.0
Opened: Apr 01, 2022 Severity: 3-Major
When an SSL client connects to the BIG-IP system using TLS 1.3 and sends an empty certificate, the CLIENTSSL_CLIENTCERT iRule event is not triggered.
CLIENTSSL_CLIENTCERT irules aren't triggered.
-- Virtual server configured on BIG-IP with SSL and iRule added -- Client authentication for client certificates is set to "request" -- iRule relying on CLIENTSSL_CLIENTCERT -- A client connects to BIG-IP using TLSv1.3 protocol without a certificate(empty certificate)
None
CLIENTSSL_CLIENTCERT iRules are now triggered when an SSL client connects to BIG-IP with TLS1.3 and sends an empty certificate message.
CLIENTSSL_CLIENTCERT iRules are now triggered when an SSL client connects to BIG-IP with TLS1.3 and sends an empty certificate message.