GHSA-gf2v-9hp6-44qg org.apache.hive:hive, org.apache.hive:hive-exec, and org.apache.hive:hive-service vulnerable to Improper Certificate Validation

• Maven org.apache.hive:hive: < 1.2.2 → fixed in 1.2.2 • Maven org.apache.hive:hive: >= 2.0.0, < 2.0.1 → fixed in 2.0.1 • Maven org.apache.hive:hive-service: < 1.2.2 → fixed in 1.2.2 • Maven org.apache.hive:hive-service: >= 2.0.0, < 2.0.1 → fixed in 2.0.1 • Maven org.apache.hive:hive-exec: < 1.2.2 → fixed in 1.2.2 • Maven org.apache.hive:hive-exec: >= 2.0.0, < 2.0.1 → fixed in 2.0.1

Apache Hive (JDBC + HiveServer2) implements SSL for plain TCP and HTTP connections (it supports both transport modes). While validating the server's certificate during the connection setup, the client in Apache Hive before 1.2.2 and 2.0.x before 2.0.1 doesn't seem to be verifying the common name attribute of the certificate. In this way, if a JDBC client sends an SSL request to server abc.com, and the server responds with a valid certificate (certified by CA) but issued to xyz.com, the client will accept that as a valid certificate and the SSL handshake will go through.