ABB Symphony + Operations 3.3

The affected versions of S+ Operations (version 2.1 SP1 and earlier) used an approach for user authentication which relies on validation at the client node (client-side authentication). This is not as secure as having the server validate a client application before allowing a connection. Therefore, if the network communication or endpoints for these applications are not protected, unauthorized actors can bypass authentication and make unauthorized connections to the server application.

Published: 2020-12-22T21:19:10.709Z
Updated: 2024-09-17T01:36:41.524Z

In S+ Operations and S+ Historian, the passwords of internal users (not Windows Users) are encrypted but improperly stored in a database.

Published: 2020-12-22T21:18:37.038Z
Updated: 2024-09-17T01:51:49.326Z

A S+ Operations and S+ Historian service is subject to a DoS by special crafted messages. An attacker might use this flaw to make it crash or even execute arbitrary code on the machine where the service is hosted.

Published: 2020-12-22T21:17:12.753Z
Updated: 2024-09-17T01:20:53.487Z

An authenticated user might execute malicious code under the user context and take control of the system. S+ Operations or S+ Historian database is affected by multiple vulnerabilities such as the possibility to allow remote authenticated users to gain high privileges.

Published: 2020-12-22T21:13:13.833Z
Updated: 2024-09-17T02:51:56.476Z

Vulnerabilities in the S+ Operations and S+ Historian web applications can lead to a possible code execution and privilege escalation, redirect the user somewhere else or download unwanted data.

Published: 2020-12-22T21:16:37.411Z
Updated: 2024-09-17T04:00:06.225Z