CVE-2016-3083
HIGHCVE-2016-3083 is a high-severity (CVSS 7.5) CWE-295 vulnerability in org.apache.hive:hive. O3 Security confirms whether CVE-2016-3083 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
org.apache.hive:hive, org.apache.hive:hive-exec, and org.apache.hive:hive-service vulnerable to Improper Certificate Validation
Blast Radius
org.apache.hive:hive☕org.apache.hive:hive☕org.apache.hive:hive-service☕org.apache.hive:hive-service☕org.apache.hive:hive-exec☕org.apache.hive:hive-execReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.hive:hive | all versions | 1.2.2 |
| ☕Maven | org.apache.hive:hive | ≥ 2.0.0&&< 2.0.1 | 2.0.1 |
| ☕Maven | org.apache.hive:hive-service | all versions | 1.2.2 |
| ☕Maven | org.apache.hive:hive-service | ≥ 2.0.0&&< 2.0.1 | 2.0.1 |
| ☕Maven | org.apache.hive:hive-exec | all versions | 1.2.2 |
| ☕Maven | org.apache.hive:hive-exec | ≥ 2.0.0&&< 2.0.1 | 2.0.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.hive:hive. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.apache.hive:hive to 1.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-3083 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2016-3083 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2016-3083. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2016-3083 in your dependencies?
O3 detects CVE-2016-3083 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.