First published: Tue May 30 2017(Updated: )
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.
Credit: security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
Apache Hive | =0.13.0 | |
Apache Hive | =0.13.1 | |
Apache Hive | =0.14.0 | |
Apache Hive | =1.0.0 | |
Apache Hive | =1.0.1 | |
Apache Hive | =1.1.0 | |
Apache Hive | =1.1.1 | |
Apache Hive | =1.2.0 | |
Apache Hive | =1.2.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-3083 is classified as a moderate severity vulnerability due to the potential for man-in-the-middle attacks.
To fix CVE-2016-3083, upgrade to Apache Hive version 1.2.2 or 2.0.1 or later.
Apache Hive versions 0.13.0 through 1.2.1, and 2.0.x before 2.0.1 are affected by CVE-2016-3083.
CVE-2016-3083 allows for man-in-the-middle attacks because the client does not properly validate the server certificate.
Yes, CVE-2016-3083 is relevant for both JDBC connections and HiveServer2 connections in Apache Hive.