Skip to content

org.apache.hive:hive, org.apache.hive:hive-exec, and org.apache.hive:hive-service vulnerable to Improper Certificate Validation

High severity GitHub Reviewed Published Mar 14, 2019 to the GitHub Advisory Database • Updated Jan 11, 2023

Package

maven org.apache.hive:hive (Maven)

Affected versions

< 1.2.2
= 2.0.0

Patched versions

1.2.2
2.0.1
maven org.apache.hive:hive-exec (Maven)
< 1.2.2
= 2.0.0
1.2.2
2.0.1
maven org.apache.hive:hive-service (Maven)
< 1.2.2
= 2.0.0
1.2.2
2.0.1

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.

References

Published to the GitHub Advisory Database Mar 14, 2019
Reviewed Jun 16, 2020
Last updated Jan 11, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

EPSS score

0.119%
(47th percentile)

Weaknesses

CVE ID

CVE-2016-3083

GHSA ID

GHSA-gf2v-9hp6-44qg

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.