Strix
26.1K

CVE-2016-3083

UnknownEPSS 1.01%

Last modified

CVE-2016-3083 is a vulnerability of currently unknown severity. 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. EPSS estimates a 1.01% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
1.01%

58.5th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
ApacheHive0.13.0
ApacheHive0.13.1
ApacheHive0.14.0
ApacheHive1.0.0
ApacheHive1.0.1
ApacheHive1.1.0
ApacheHive1.1.1
ApacheHive1.2.0
ApacheHive1.2.1

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is 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.
How severe is CVE-2016-3083?
Severity scoring for CVE-2016-3083 is pending analysis. The EPSS model estimates a 1.01% probability of exploitation in the next 30 days.
How do I fix CVE-2016-3083?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2016

View all 2016CVEs →

Are you affected by CVE-2016-3083?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST