Skip to content

Incorrect Permission Assignment for Critical Resource in Apache hive

Low severity GitHub Reviewed Published Nov 21, 2018 to the GitHub Advisory Database • Updated Jan 9, 2023

Package

maven org.apache.hive:hive (Maven)

Affected versions

>= 2.1.0, < 2.3.3

Patched versions

2.3.3
maven org.apache.hive:hive-exec (Maven)
>= 2.1.0, < 2.3.3
2.3.3
maven org.apache.hive:hive-service (Maven)
>= 2.1.0, < 2.3.3
2.3.3

Description

In Apache Hive 2.1.0 to 2.3.2, when 'COPY FROM FTP' statement is run using HPL/SQL extension to Hive, a compromised/malicious FTP server can cause the file to be written to an arbitrary location on the cluster where the command is run from. This is because FTP client code in HPL/SQL does not verify the destination location of the downloaded file. This does not affect hive cli user and hiveserver2 user as hplsql is a separate command line script and needs to be invoked differently.

References

Published to the GitHub Advisory Database Nov 21, 2018
Reviewed Jun 16, 2020
Last updated Jan 9, 2023

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

EPSS score

0.155%
(53rd percentile)

Weaknesses

CVE ID

CVE-2018-1315

GHSA ID

GHSA-p639-xxv5-j383

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.