TLSVersion IBM data server driver configuration keyword
Sets the desired version of the Transport Layer Security (TLS) protocol for a TLS connection.
In response to CVE-2023-32342, Db2 releases with KI DT223175 uses the non-FIPS IBM Crypto for C (ICC) for TLS ciphers that use RSA key exchange, as the FIPS certified ICC is vulnerable to CVE-2023-32342. Customers with a requirement to use only FIPS 140 certified cryptographic modules must enable Strict FIPS mode.
Note: The FIPS certified ICC is unavailable on 32-bit and MacOS platforms. Db2® automatically switches to using the non-FIPS ICC if on those platforms.
In strict FIPS mode, Db2 releases with KI DT223175 disable all TLS ciphers and versions that are vulnerable to CVE-2023-32342.
- TLS 1.0 and 1.1 are disabled in strict mode regardless of the SSL_VERSIONS setting, as the only supported ciphers use RSA key exchange. If the SSL_VERSIONS DBM CFG parameter is unset, or is set to TLSV1, TLS 1.2 is enabled in its place.
- TLS 1.2 ciphers that use RSA key exchange (TLS_RSA_*) are disabled. If there are no remaining ciphers in the SSL_CIPHERSPECS DBM CFG parameter, the SSL environment fails to initialize. For instances using RSA certificates, the SSL_CIPHERSPECS DBM CFG parameter must be configured to use TLS_ECDHE_RSA ciphers for no certificate changes to be required.
- TLS 1.3 is unaffected by CVE-2023-32342, and behavior does not change in strict FIPS mode.
- Equivalent CLI keyword
- TLSVersion
- Equivalent IBM® data server provider for .NET connection string keyword
- TLSVersion
- IBM data server driver configuration file (db2dsdriver.cfg) syntax
<parameter name="TLSVersion" value="TLSV1 | TLSV12 | TLSV13"/>- Default setting:
- None
- Usage notes:
-
This option sets the desired version of the TLS protocol for a TLS connection. When the
TLSVersionparameter is not set, or is set to NULL, TLS 1.2 and TLS 1.3 are enabled. In Db2 versions prior to 11.5.9, and Db2 11.5.8 releases without KI DT245990, all TLS versions are enabled.