November 20, 2019
IBM Operations Analytics - Log Analysis is prone to multiple security vulnerabilities. Successful exploits will allow an attacker to obtain sensitive information, insert a crafted host header to navigate the victim to the attacker's domain or compromise the affected application. Other attacks are also possible. IBM Operations Analytics - Log Analysis versions 1.3.1 through 1.3.5 are vulnerable.
- IBM Operations Analytics - Log Analysis 1.3.1
- IBM Operations Analytics - Log Analysis 1.3.2
- IBM Operations Analytics - Log Analysis 1.3.3
- IBM Operations Analytics - Log Analysis 188.8.131.52
- IBM Operations Analytics - Log Analysis 1.3.4
- IBM Operations Analytics - Log Analysis 1.3.5
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.
Run all software as a nonprivileged user with minimal access rights.
Run all non-administrative software as a non-administrative user with the least amount of privileges required to successfully operate. This will greatly reduce the potential damage that successful exploitation may achieve.
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 suspicious URI sequences. Review webserver logs frequently.
Do not accept or execute files from untrusted or unknown sources.
To reduce the likelihood of successful exploits, never handle files that originate from unfamiliar or untrusted sources.
Do not follow links provided by unknown or untrusted sources.
Never follow links provided by unknown or untrusted sources.
Updates are available. Please see the references or vendor advisory for more information.
© 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.