Apache Software Foundation Hive 0.14.0
Approved changes feed: RSS · Atom
cpe:2.3:a:apache:hive:0.14.0:*:*:*:*:*:*:*
part: a version: 0.14.0 update: *
| Vendor | Apache (b0303047-b7dd-5cf8-abcc-71b7d9d80b95) |
|---|---|
| Product | Hive (4541c929-03da-5484-b3ec-91ff2b50e276) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:apache/hive |
purl2cpe | 2026-06-01 10:14:29.316106 |
pkg:github/apache/hive |
purl2cpe | 2026-06-01 10:14:29.316108 |
pkg:maven/org.apache.hive/hive |
purl2cpe | 2026-06-01 10:14:29.316110 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2016-3083 |
vulnerable | 2026-06-08 05:07:44.337127 |
Details available
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-30T14:00:00.000Z
Updated: 2024-08-05T23:40:15.584Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.