CVE-2016-3083

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.

Published: 2017-05-30 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2016-3083 is rated Moderate Risk (51.2/100): CVSS High severity, with medium exploitation likelihood (EPSS 1.01%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2016-3083

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.21% 1.01% +0.80%
2 2025-06-17 0.49% 0.21% -0.28%
3 2025-03-30 — 0.49% —

Full EPSS history (7 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2016-3083

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.0 HIGH
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]
5.0 2.0 MEDIUM
AV:N/AC:L/Au:N/C:N/I:P/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:N)
No availability impact.
 10.0 2.9 [email protected]

Weakness enumeration for CVE-2016-3083

GitHub Security Advisory for CVE-2016-3083

GHSA-gf2v-9hp6-44qg · Severity: high · Ecosystem: maven — org.apache.hive:hive, org.apache.hive:hive-exec, and org.apache.hive:hive-service vulnerable to Improper Certificate Validation

Affected software / configurations for CVE-2016-3083

Vendor Product Version Raw CPE
apache hive 0.13.0 cpe:2.3:a:apache:hive:0.13.0:*:*:*:*:*:*:*
apache hive 0.13.1 cpe:2.3:a:apache:hive:0.13.1:*:*:*:*:*:*:*
apache hive 0.14.0 cpe:2.3:a:apache:hive:0.14.0:*:*:*:*:*:*:*
apache hive 1.0.0 cpe:2.3:a:apache:hive:1.0.0:*:*:*:*:*:*:*
apache hive 1.0.1 cpe:2.3:a:apache:hive:1.0.1:*:*:*:*:*:*:*
apache hive 1.1.0 cpe:2.3:a:apache:hive:1.1.0:*:*:*:*:*:*:*
apache hive 1.1.1 cpe:2.3:a:apache:hive:1.1.1:*:*:*:*:*:*:*
apache hive 1.2.0 cpe:2.3:a:apache:hive:1.2.0:*:*:*:*:*:*:*
apache hive 1.2.1 cpe:2.3:a:apache:hive:1.2.1:*:*:*:*:*:*:*

References for CVE-2016-3083

cvelogic Threat Intelligence