CVE-2018-1314 json
Moderate severity vulnerability that affects org.apache.hive:hive-jdbc
published 8y ago modified 4mo ago also GHSA-jmf4-pq78-f8vj , EUVD-2018-0760
- cvss
- 4.3
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 80%
- public exploits
- 0
- none known
Summary
In Apache Hive 2.3.3, 3.1.0 and earlier, 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.
Patch / fix
- maven org.apache.hive:hive-jdbc 2.3.4, 3.1.1
Is CVE-2018-1314 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.99% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 4.3 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
| GitHub | 3.0 | 4.3 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.hive:hive-jdbc | <2.3.4 >=3.0.0, <3.1.1 |
2.3.4 3.1.1 |
Affected products
- Apache Software Foundation Apache Hive
Classification
- Weakness
-
- CWE-862 Missing Authorization
References
-
securityfocus.com
/bid/105884
vdb-entry, web, third-party-advisory
- lists.apache.org /thread.html/3da47dbcbf09697387f29d2f1aed970523b6b334d93afd3cced23727%40%3Cdev.hive.apache.org%3E
-
nvd.nist.gov
/vuln/detail/CVE-2018-1314
advisory
-
github.com
/advisories/GHSA-jmf4-pq78-f8vj
advisory
-
lists.apache.org
/thread.html/3da47dbcbf09697387f29d2f1aed970523b6b334d93afd3cced23727@%3Cdev.hive.apache.org%3E
web
Sources
- CVE List CVE-2018-1314
- GitHub Advisory GHSA-jmf4-pq78-f8vj
- NVD CVE-2018-1314
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.