Spring Boot's Cassandra SSL auto-configuration disables TLS hostname verification
Spring Boot
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.boot:spring-boot-cassandra Maven |
|
|
Spring Boot
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.boot:spring-boot-cassandra Maven |
|
|
Spring Boot's Cassandra auto-configuration does not perform hostname verification when establishing an SSL connection to Cassandra.
Affected: Spring Boot 4.0.0–4.0.5 (fix 4.0.6), 3.5.0–3.5.13 (fix 3.5.14), 3.4.0–3.4.15 (fix 3.4.16), 3.3.0–3.3.18 (fix 3.3.19), 2.7.0–2.7.32 (fix 2.7.33); Cassandra SSL auto-configuration. Versions that are no longer supported are also affected per vendor advisory.
From the CVE record · vmware
Spring Boot's Cassandra auto-configuration does not verify the server hostname when establishing an SSL connection. A network attacker could take advantage of this when an affected application connects to Cassandra over SSL. The input does not specify whether authentication or user interaction is required.
Engineers running Spring Boot Cassandra SSL auto-configuration should check versions 4.0.0–4.0.5, 3.5.0–3.5.13, 3.4.0–3.4.15, 3.3.0–3.3.18, and 2.7.0–2.7.32; the vendor also identifies unsupported versions as affected.