Non notée
CVE-2017-9792 In Apache Impala (incubating) before 2.10.0, a malicious user with "ALTER" permissions on an Impala table can access any…
Description
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.
Produits et versions touchés
| Produit | Versions touchées | Corrigé en |
|---|---|---|
| Apache Impala | Versions non publiées |
Références
- issues.apache.org issues.apache.org
- 101173 www.securityfocus.com
- [announce] 20170929 CVE-2017-9792 Apache Impala (incubating) Information Disclosure lists.apache.org
Chronologie
- Publiée
- Dernière modification
Autres CVE de Apache Impala
Les 13 CVE de Apache Impala →
CVE-2026-93684
An SQL user using Impala up to and including version 4.5.2 with only SELECT permission can put JavaScript in a table…
Non notée
CVE-2026-90466
Path traversal of 'trusted_jar_paths' in Impala 4.5.2 allows an attacker-controlled JAR to be loaded via a relative path…
Non notée
CVE-2026-97720
Incorrect implementation of JWT/OAuth authentication in Impala executors in Apache Impala versions up to and including…
Non notée
CVE-2026-65181
Insufficient authorization of Data Source tables in Impala 2.7-4.5 allows a client with privileges to upload a file to…
Non notée