Approved changes feed: RSS · Atom

cpe:2.3:a:apache:impala:2.9.0:*:*:*:*:*:*:*

part: a version: 2.9.0 update: *

VendorApache (b0303047-b7dd-5cf8-abcc-71b7d9d80b95)
ProductImpala (20866daa-77eb-502d-a57a-648c9a68b410)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
pkg:apache/impala purl2cpe 2026-06-01 10:14:28.386402
pkg:docker/apache/impala purl2cpe 2026-06-01 10:14:28.386404
pkg:github/apache/impala purl2cpe 2026-06-01 10:14:28.386405

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2017-9792 vulnerable 2026-06-08 05:10:10.591257 Details available
In Apache Impala (incubating) before 2.10.0, a malicious user with "ALTER" permissions on an Impala table can access any other Kudu table data by altering the table properties to make it "external" and then changing the underlying table mapping to point to other Kudu tables. This violates and works around the authorization requirement that creating a Kudu external table via Impala requires an "ALL" privilege at the server scope. This privilege requirement for "CREATE" commands is enforced to precisely avoid this scenario where a malicious user can change the underlying Kudu table mapping. The fix is to enforce the same privilege requirement for "ALTER" commands that would make existing non-external Kudu tables external.
Published: 2017-10-03T01:00:00.000Z
Updated: 2024-09-17T04:24:31.508Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.