CVE Catalog

CVE-2016-3083

High
Published: Translated: NVD NIST

Summary

Apache Hive (JDBC + HiveServer2) before version 1.2.2 and 2.0.x before 2.0.1 does not verify the common name attribute of the certificate during SSL connection setup. This allows a certificate issued for a different domain to be accepted, potentially leading to man-in-the-middle attacks.

Risk Assessment

The lack of common name verification increases the risk of data interception by unauthorized entities, which can lead to serious security breaches within the organization.

Recommendation

It is recommended to upgrade Apache Hive to version 1.2.2 or 2.0.1 and enable common name verification in the SSL configuration.

Related vulnerabilities

Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS