CVE-2016-3083: High severity apache hive vulnerability
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2016-3083?
CVE-2016-3083 is classified as a moderate severity vulnerability due to the potential for man-in-the-middle attacks.
How do I fix CVE-2016-3083?
To fix CVE-2016-3083, upgrade to Apache Hive version 1.2.2 or 2.0.1 or later.
Which versions of Apache Hive are affected by CVE-2016-3083?
Apache Hive versions 0.13.0 through 1.2.1, and 2.0.x before 2.0.1 are affected by CVE-2016-3083.
What type of attack is possible due to CVE-2016-3083?
CVE-2016-3083 allows for man-in-the-middle attacks because the client does not properly validate the server certificate.
Is CVE-2016-3083 relevant for both JDBC and HiveServer2 connections?
Yes, CVE-2016-3083 is relevant for both JDBC connections and HiveServer2 connections in Apache Hive.