Missing Authentication for Critical Function in Apache Calcite
Apache Calcite
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.calcite:calcite-core Maven |
|
|
| org.apache.calcite:calcite-druid Maven |
|
|
| org.apache.calcite:calcite-splunk |
Apache Calcite
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.calcite:calcite-core Maven |
|
|
| org.apache.calcite:calcite-druid Maven |
|
|
| org.apache.calcite:calcite-splunk |
|
|
HttpUtils#getURLConnection method disables explicitly hostname verification for HTTPS connections making clients vulnerable to man-in-the-middle attacks. Calcite uses internally this method to connect with Druid and Splunk so information leakage may happen when using the respective Calcite adapters. The method itself is in a utility class so people may use it to create vulnerable HTTPS connections for other applications. From Apache Calcite 1.26 onwards, the hostname verification will be performed using the default JVM truststore.
From the CVE record · apache
HttpUtils#getURLConnection disables hostname verification for HTTPS connections, making them vulnerable to man-in-the-middle attacks. Calcite uses this method for its Druid and Splunk adapters, where information may leak; applications using the utility method may also create vulnerable HTTPS connections.
Teams using Maven packages org.apache.calcite:calcite-core, org.apache.calcite:calcite-druid, or org.apache.calcite:calcite-splunk before version 1.26.0 should check their deployments.