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…

A S+ Operations and S+ Historian service is subject to a DoS by special crafted messages

In S+ Operations and S+ History, it is possible that an unauthenticated user could inject values to the Operations History server (or standalone S+ History server) and ultimately…

In S+ Operations and S+ Historian, a successful SQL injection exploit can read sensitive data from the database, modify database data (Insert/Update/Delete), execute…

An authenticated user might execute malicious code under the user context and take control of the system

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…

In S+ Operations and S+ Historian, not all client commands correctly check user permission as expected

In Symphony Plus Operations and Symphony Plus Historian, some services can be vulnerable to privilege escalation attacks

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