AWS redshift: Redshift JDBC SSLMode default changed to verify-full
Summary
Documents that the Redshift JDBC driver default for SSLMode is now verify-full (driver 2.3.0+) instead of verify-ca, and explains that without an explicit SSLMode the driver only logs a warning and connects when the server certificate does not match the host name.
Security assessment
Changing the default SSLMode from verify-ca to verify-full enables hostname verification of the server certificate, mitigating man-in-the-middle/impersonation attacks against TLS connections; the added note also warns that omitting SSLMode results in only a logged warning rather than enforcement, which is security-relevant hardening guidance. No specific CVE or incident is referenced.
Evidence
+ * Default Value – verify-full
Diff
diff --git a/redshift/latest/mgmt/jdbc20-configuration-options.md b/redshift/latest/mgmt/jdbc20-configuration-options.md index 5ad5c87..f50af55 100644 --- a//redshift/latest/mgmt/jdbc20-configuration-options.md +++ b//redshift/latest/mgmt/jdbc20-configuration-options.md @@ -1465 +1465 @@ This parameter is required if SSLCert is specified. - * Default Value – verify-ca + * Default Value – verify-full @@ -1491,0 +1492,2 @@ We recommend using `verify-full` for SSL connections whenever possible. +In driver versions 2.3.0 and later, the default is `verify-full`. In earlier versions, the default was `verify-ca`. If you don't set `SSLMode` and the server certificate doesn't match the host name, the driver logs a warning and connects. If you set `SSLMode`, the driver enforces the mode that you set. +