Skip to content
Fencer Intel
high 8.3

CVE-2015-7521 json

High severity vulnerability that affects org.apache.hive:hive, org.apache.hive:hive-exec, and org.apache.hive:hive-service

published 10y ago modified 4mo ago also GHSA-83r3-c79w-f6wc , EUVD-2018-0737

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

Summary

The authorization framework in Apache Hive 1.0.0, 1.0.1, 1.1.0, 1.1.1, 1.2.0 and 1.2.1, on clusters protected by Ranger and SqlStdHiveAuthorization, allows attackers to bypass intended parent table access restrictions via unspecified partition-level operations.

Patch / fix

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

Is CVE-2015-7521 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 Fencer

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-2015-7521 updated cvss 6.8

Hive: authorization vulnerability

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

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

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

CVSS scores

assigned by version score vector
NVD 3.0 8.3 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.0 8.3 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L

Affected packages

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

Classification

Weakness

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.