Description
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.
Remediation
References
http://www.securityfocus.com/bid/98669
https://lists.apache.org/thread.html/0851bcf85635385f94cdaa008053802d92b4aab0a3075e30ed171192%40%3Cdev.hive.apache.org%3E
Related Vulnerabilities
CVE-2018-1000151 Vulnerability in maven package org.jenkins-ci.plugins:vsphere-cloud
CVE-2018-11775 Vulnerability in maven package org.apache.activemq:activemq-all
CVE-2023-1664 Vulnerability in maven package org.keycloak:keycloak-core
CVE-2018-1999035 Vulnerability in maven package com.inedo.buildmaster:inedo-buildmaster
CVE-2018-17187 Vulnerability in maven package org.apache.qpid:proton-j