Vulnerability 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.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Apache | Hive | 0.13.0 |
Related Weaknesses (CWE)
References
- http://www.securityfocus.com/bid/98669
- https://lists.apache.org/thread.html/0851bcf85635385f94cdaa008053802d92b4aab0a30
- http://www.securityfocus.com/bid/98669
- https://lists.apache.org/thread.html/0851bcf85635385f94cdaa008053802d92b4aab0a30
FAQ
What is CVE-2016-3083?
CVE-2016-3083 is a vulnerability with a CVSS score of 7.5 (HIGH). 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...
How severe is CVE-2016-3083?
CVE-2016-3083 has been rated HIGH with a CVSS base score of 7.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2016-3083?
Check the references section above for vendor advisories and patch information. Affected products include: Apache Hive.