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.
Metrics
Affected Vendors & Products
References
History
No history.
MITRE
Status: PUBLISHED
Assigner: apache
Published: 2017-10-03T01:00:00Z
Updated: 2024-09-17T04:24:31.508Z
Reserved: 2017-06-21T00:00:00
Link: CVE-2017-9792
Vulnrichment
No data.
NVD
Status : Modified
Published: 2017-10-04T01:29:03.840
Modified: 2024-11-21T03:36:51.783
Link: CVE-2017-9792
Redhat
No data.