Trend Micro Apex One CVE-2019-18188 Command Injection Vulnerability

Risk

High

Date Discovered

October 28, 2019

Description

Trend Micro Apex One is prone to a command-injection vulnerability because it fails to properly sanitize user-supplied input. Successfully exploiting this issue may allow an attacker to execute arbitrary code in the context of the affected application. Failed exploit attempts will result in a denial-of-service condition. Versions prior to Trend Micro Apex One (on premise) 2019 Build 2049 are vulnerable.

Technologies Affected

  • Trend Micro Apex One (on premise)

Recommendations

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.

Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to monitor the network for suspicious requests. This may help detect attacks that try to exploit this and similar vulnerabilities. Audit all applicable logs regularly

Run all software as a nonprivileged user with minimal access rights.
To reduce the impact of latent vulnerabilities, run all server processes with the minimal amount of privileges required for functionality.

Updates are available. Please see the references or vendor advisory for more information.

References

Credits

Trend Micro Research


© 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 secure@symantec.com.

Disclaimer

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 secure@symantec.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.