November 4, 2019
Apache Impla is prone to a authorization-bypass vulnerability. An attacker can exploit this issue to bypass certain security restrictions and perform unauthorized actions or gain elevated privileges; this may aid in launching further attacks. Apache Impala versions 2.7.0 through 3.2.0 are vulnerable.
- Apache Impala 2.7.0
- Apache Impala 2.8.0
- Apache Impala 2.9.0
- Apache Impala 3.0
- Apache Impala 3.0.1
- Apache Impala 3.1.0
- Apache Impala 3.2.0
Block external access at the network boundary, unless external parties require service.
If possible, block external access to the server hosting the vulnerable software. Permit access for trusted or internal networks and computers only.
Run all software as a nonprivileged user with minimal access rights.
Running server processes with minimal privileges and within a restricted environment using facilities such as chroot or jail may limit the consequences of successful attacks.
Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to monitor network traffic for signs of anomalous or suspicious activity such as unexplained incoming and outgoing traffic. This may indicate exploit attempts or activity that results from successful exploits.
Updates are available. Please see the references or vendor advisory for more information.
The vendor reported this issue.
© 1995- Symantec Corporation
Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from firstname.lastname@example.org.
The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.
Symantec, Symantec products, Symantec Security Response, and email@example.com are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.