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-2019-10317 Vulnerability in maven package org.jvnet.hudson.plugins:sitemonitor
CVE-2020-2252 Vulnerability in maven package org.jenkins-ci.plugins:mailer
CVE-2022-32210 Vulnerability in maven package org.webjars.npm:undici
CVE-2022-22885 Vulnerability in maven package cn.hutool:hutool-http
CVE-2012-5817 Vulnerability in maven package org.codehaus.xfire:xfire-core