A vulnerability exists in the query validation of the MicroSCADA Pro/X SYS600 product. If exploited this could allow an authenticated attacker to inject code towards persistent data. Note that to successfully exploit this vulnerability an attacker must have a valid credential.
The product generates a query intended to access or manipulate data in a data store such as a database, but it does not neutralize or incorrectly neutralizes special elements that can modify the intended logic of the query.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Microscada_pro_sys600 | Hitachienergy | 9.4-fixpack_2_hf1 (including) | 9.4-fixpack_2_hf1 (including) |
| Microscada_pro_sys600 | Hitachienergy | 9.4-fixpack_2_hf2 (including) | 9.4-fixpack_2_hf2 (including) |
| Microscada_pro_sys600 | Hitachienergy | 9.4-fixpack_2_hf3 (including) | 9.4-fixpack_2_hf3 (including) |
| Microscada_pro_sys600 | Hitachienergy | 9.4-fixpack_2_hf4 (including) | 9.4-fixpack_2_hf4 (including) |
| Microscada_pro_sys600 | Hitachienergy | 9.4-fixpack_2_hf5 (including) | 9.4-fixpack_2_hf5 (including) |
| Microscada_x_sys600 | Hitachienergy | 10.0 (including) | 10.6 (excluding) |
Depending on the capabilities of the query language, an attacker could inject additional logic into the query to:
The ability to execute additional commands or change which entities are returned has obvious risks. But when the product logic depends on the order or number of entities, this can also lead to vulnerabilities. For example, if the query expects to return only one entity that specifies an administrative user, but an attacker can change which entities are returned, this could cause the logic to return information for a regular user and incorrectly assume that the user has administrative privileges. While this weakness is most commonly associated with SQL injection, there are many other query languages that are also subject to injection attacks, including HTSQL, LDAP, DQL, XQuery, Xpath, and “NoSQL” languages.