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.
References
Configurations
Configuration 1 (hide)
|
History
21 Nov 2024, 02:49
Type | Values Removed | Values Added |
---|---|---|
References | () http://www.securityfocus.com/bid/98669 - | |
References | () https://lists.apache.org/thread.html/0851bcf85635385f94cdaa008053802d92b4aab0a3075e30ed171192%40%3Cdev.hive.apache.org%3E - |
07 Nov 2023, 02:32
Type | Values Removed | Values Added |
---|---|---|
References |
|
|
Information
Published : 2017-05-30 14:29
Updated : 2024-11-21 02:49
NVD link : CVE-2016-3083
Mitre link : CVE-2016-3083
CVE.ORG link : CVE-2016-3083
JSON object : View
Products Affected
apache
- hive
CWE
CWE-295
Improper Certificate Validation