CVE-2016-3083
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.
How to fix
- org.apache.hive:hive1.2.2, 2.0.1 or later
- org.apache.hive:hive-service1.2.2, 2.0.1 or later
- org.apache.hive:hive-exec1.2.2, 2.0.1 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| apache hive | 0.13.0, 0.13.1, 0.14.0, 1.0.0, 1.0.1, 1.1.0, 1.1.1, 1.2.0, 1.2.1 | — |
| org.apache.hive:hiveMaven | v < 1.2.2, 2.0.0 ≤ v < 2.0.1 | 1.2.2, 2.0.1 |
| org.apache.hive:hive-serviceMaven | v < 1.2.2, 2.0.0 ≤ v < 2.0.1 | 1.2.2, 2.0.1 |
| org.apache.hive:hive-execMaven | v < 1.2.2, 2.0.0 ≤ v < 2.0.1 | 1.2.2, 2.0.1 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.