CVE Vulnerabilities

CVE-2020-7545

Improper Access Control

Published: Dec 01, 2020 | Modified: Nov 21, 2024
CVSS 3.x
7.2
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
6.5 MEDIUM
AV:N/AC:L/Au:S/C:P/I:P/A:P
RedHat/V2
RedHat/V3
Ubuntu

A CWE-284:Improper Access Control vulnerability exists in EcoStruxureª and SmartStruxureª Power Monitoring and SCADA Software (see security notification for version information) that could allow for arbitrary code execution on the server when an authorized user access an affected webpage.

Weakness

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

Affected Software

Name Vendor Start Version End Version
Ecostruxure_energy_expert Schneider-electric 2.0 (including) 2.0 (including)
Ecostruxure_power_monitoring_expert Schneider-electric 7.0 (including) 7.0 (including)
Ecostruxure_power_monitoring_expert Schneider-electric 8.0 (including) 8.0 (including)
Ecostruxure_power_monitoring_expert Schneider-electric 9.0 (including) 9.0 (including)
Power_manager Schneider-electric 1.1 (including) 1.1 (including)
Power_manager Schneider-electric 1.2 (including) 1.2 (including)
Power_manager Schneider-electric 1.3 (including) 1.3 (including)
Powerscada_expert_with_advanced_reporting_and_dashboards Schneider-electric 8.0 (including) 8.0 (including)
Powerscada_operation_with_advanced_reporting_and_dashboards Schneider-electric 9.0 (including) 9.0 (including)

Extended Description

Access control involves the use of several protection mechanisms such as:

When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses:

Potential Mitigations

  • Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
  • Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References