Skip to content
Fencer Intel
low 3.7

CVE-2018-1284 json

Exposure of Sensitive Information to an Unauthorized Actor in Apache hive

published 2018-04-05 8 y ago modified 2026-06-17 4 mo ago also GHSA-rxmr-c9jm-7mm8 , EUVD-2018-0777

cvss
3.7
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.1%
EPSS 2.1% chance of exploitation in 30 days, percentile 82%
public exploits
0
none known

Summary

In Apache Hive 0.6.0 to 2.3.2, malicious user might use any xpath UDFs (xpath/xpath_string/xpath_boolean/xpath_number/xpath_double/xpath_float/xpath_long/xpath_int/xpath_short) to expose the content of a file on the machine running HiveServer2 owned by HiveServer2 user (usually hive) if hive.server2.enable.doAs=false.

Patch / fix

  • maven org.apache.hive:hive 2.3.3
  • maven org.apache.hive:hive-exec 2.3.3
  • maven org.apache.hive:hive-service 2.3.3

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-1284 updated cvss 6.5

hive: Mishandled input in UDFXPathUtil.java allows users to access arbitrary files via crafted XML

  • Red Hat JBoss Fuse Integration Service 2 hive
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.15% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 3.7 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N
GitHub 3.0 3.7 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.apache.hive:hive
>=0.6.0, <2.3.3
2.3.3
maven org.apache.hive:hive-exec
>=0.6.0, <2.3.3
2.3.3
maven org.apache.hive:hive-service
>=0.6.0, <2.3.3
2.3.3

Affected products

  • Apache Software Foundation Apache Hive

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

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.