Moxa AWK-3121 Series ICSA-19-337-02 Multiple Security Vulnerabilities

Risk

High

Date Discovered

December 2, 2019

Description

Moxa AWK-3121 Series is prone to the following security vulnerabilities: 1. Multiple information-disclosure vulnerabilities 2. A security-bypass vulnerability 3. Multiple buffer-overflow vulnerabilities 4. A cross-site request-forgery vulnerability 5. Multiple command-injection vulnerabilities 6. A cross-site scripting vulnerability Attackers can exploit these issues to execute arbitrary code or commands, obtain sensitive information, execute arbitrary script-code in the browser of an unsuspecting user in the context of the affected site or bypass certain security restrictions and perform unauthorized actions. Moxa AWK-3121 Series version 1.14 and prior are vulnerable.

Technologies Affected

  • Moxa AWK-3121 Series 1.14

Recommendations

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.
To reduce the impact of latent vulnerabilities, always run nonadministrative software as an unprivileged user with minimal access rights.

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 may indicate exploit attempts or activity that results from successful exploits.

Do not follow links provided by unknown or untrusted sources.
Web users should be cautious about following links to sites that are provided by unfamiliar or suspicious sources. Filtering HTML from emails may help remove a possible vector for transmitting malicious links to users.

Set web browser security to disable the execution of JavaScript.
Since a successful exploit of html-injection issues allows malicious code to execute in web clients, consider disabling support for script code and active content within the client browser. Note that this mitigation tactic might adversely affect legitimate websites that rely on the execution of browser-based script code.

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 memory-corruption vulnerabilities.

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

References

Credits

Samuel Huntley


© 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.