Lookup for vulnerable packages by Package URL.
| Purl | pkg:maven/org.apache.hive/hive@0.14.0 |
| Type | maven |
| Namespace | org.apache.hive |
| Name | hive |
| Version | 0.14.0 |
| Qualifiers |
|
| Subpath | |
| Is_vulnerable | true |
| Next_non_vulnerable_version | 2.3.4 |
| Latest_non_vulnerable_version | 3.1.3 |
| Affected_by_vulnerabilities |
| 0 |
|
| 1 |
| url |
VCID-jq4c-tghp-s3c8 |
| vulnerability_id |
VCID-jq4c-tghp-s3c8 |
| summary |
Missing Authorization
The Hive `EXPLAIN` operation does not check for necessary authorization of involved entities in a query. An unauthorized user can do `EXPLAIN` on arbitrary table or view and expose table metadata and statistics. |
| references |
|
| fixed_packages |
|
| aliases |
CVE-2018-1314, GHSA-jmf4-pq78-f8vj
|
| risk_score |
3.1 |
| exploitability |
0.5 |
| weighted_severity |
6.2 |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-jq4c-tghp-s3c8 |
|
| 2 |
|
| 3 |
| url |
VCID-xf72-ztd4-8kgd |
| vulnerability_id |
VCID-xf72-ztd4-8kgd |
| summary |
Improper Certificate Validation
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 does not 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 |
|
| fixed_packages |
|
| aliases |
CVE-2016-3083, GHSA-gf2v-9hp6-44qg
|
| risk_score |
4.0 |
| exploitability |
0.5 |
| weighted_severity |
8.0 |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-xf72-ztd4-8kgd |
|
|
| Fixing_vulnerabilities |
|
| Risk_score | 4.0 |
| Resource_url | http://public2.vulnerablecode.io/packages/pkg:maven/org.apache.hive/hive@0.14.0 |