What is CVE-2018-1315?

CVE-2018-1315 is a low-severity incorrect permission assignment for critical resource vulnerability in org.apache.hive:hive (maven), affecting versions >= 2.1.0, < 2.3.3. It is fixed in 2.3.3. A file, directory, or other resource is assigned permissions that allow broader access than intended.

How severe is CVE-2018-1315?

CVE-2018-1315 has a CVSS score of 3.7 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which packages are affected by CVE-2018-1315?

org.apache.hive:hive (maven) versions >= 2.1.0, = 2.1.0, = 2.1.0, < 2.3.3.

Is there a fix for CVE-2018-1315?

Yes. CVE-2018-1315 is fixed in 2.3.3. Upgrade to this version or later.

Is CVE-2018-1315 exploitable, and should I be worried?

Whether CVE-2018-1315 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2018-1315 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2018-1315 in org.apache.hive:hive

Q: How severe is CVE-2018-1315?

CVE-2018-1315 has a CVSS score of 3.7 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which packages are affected by CVE-2018-1315?

org.apache.hive:hive (maven) versions >= 2.1.0, = 2.1.0, = 2.1.0, < 2.3.3.

Q: Is there a fix for CVE-2018-1315?

Yes. CVE-2018-1315 is fixed in 2.3.3. Upgrade to this version or later.

Q: Is CVE-2018-1315 exploitable, and should I be worried?

Whether CVE-2018-1315 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2018-1315 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2018-1315?

Upgrade: org.apache.hive:hive to 2.3.3 or later, org.apache.hive:hive-exec to 2.3.3 or later, org.apache.hive:hive-service to 2.3.3 or later.

Summary

Incorrect Permission Assignment for Critical Resource in Apache hive

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.

Impact

A file, directory, or other resource is assigned permissions that allow broader access than intended. Typical impact: unauthorized read, modification, or execution of the resource.

CVE-2018-1315 has a CVSS score of 3.7 (Low). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.3.3); upgrading removes the vulnerable code path.

Affected versions

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

Security releases

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 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.apache.hive:hive to 2.3.3 or later; org.apache.hive:hive-exec to 2.3.3 or later; org.apache.hive:hive-service to 2.3.3 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2018-1315? CVE-2018-1315 is a low-severity incorrect permission assignment for critical resource vulnerability in org.apache.hive:hive (maven), affecting versions >= 2.1.0, < 2.3.3. It is fixed in 2.3.3. A file, directory, or other resource is assigned permissions that allow broader access than intended.
How severe is CVE-2018-1315? CVE-2018-1315 has a CVSS score of 3.7 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which packages are affected by CVE-2018-1315?
- org.apache.hive:hive (maven) (versions >= 2.1.0, < 2.3.3)
- org.apache.hive:hive-exec (maven) (versions >= 2.1.0, < 2.3.3)
- org.apache.hive:hive-service (maven) (versions >= 2.1.0, < 2.3.3)
Is there a fix for CVE-2018-1315? Yes. CVE-2018-1315 is fixed in 2.3.3. Upgrade to this version or later.
Is CVE-2018-1315 exploitable, and should I be worried? Whether CVE-2018-1315 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2018-1315 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2018-1315?
- Upgrade org.apache.hive:hive to 2.3.3 or later
- Upgrade org.apache.hive:hive-exec to 2.3.3 or later
- Upgrade org.apache.hive:hive-service to 2.3.3 or later

Other vulnerabilities in org.apache.hive:hive

CVE-IDSeverityPackage summary