October 1, 2019
Palo Alto Networks Zingbox Inspector is prone to a remote code-execution vulnerability. An attacker can exploit this issue to execute arbitrary code within the context of the affected system. Palo Alto Networks Zingbox Inspector version 1.293 and prior are vulnerable.
- Paloaltonetworks Zingbox Inspector 1.280
- Paloaltonetworks Zingbox Inspector 1.281
- Paloaltonetworks Zingbox Inspector 1.286
- Paloaltonetworks Zingbox Inspector 1.287
- Paloaltonetworks Zingbox Inspector 1.288
- Paloaltonetworks Zingbox Inspector 1.289
- Paloaltonetworks Zingbox Inspector 1.293
Block external access at the network boundary, unless external parties require service.
If global access isn't needed, filter access to the affected computer at the network boundary. Restricting access to only trusted computers and networks might greatly reduce the likelihood of successful exploits.
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. This includes but is not limited to requests that include NOP sleds and unexplained incoming and outgoing traffic. This will reduce the likelihood of these issues being exploited.
Run all software as a nonprivileged user with minimal access rights.
Since these issues may be leveraged to execute arbitrary code within the security context of the affected server, run the server with least privileges possible so as to reduce the severity of successful exploits.
Implement multiple redundant layers of security.
Memory-protection schemes (such as nonexecutable stack and heap configurations and randomly mapped memory segments) will complicate exploits of remote code-execution vulnerabilities.
Updates are available. Please see the references or vendor advisory for more information.
The vendor reported the 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 email@example.com.
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 firstname.lastname@example.org 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.