CVE Vulnerabilities

CVE-2021-40360

Exposure of Sensitive Information to an Unauthorized Actor

Published: Feb 09, 2022 | Modified: Nov 21, 2024
CVSS 3.x
8.8
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
4 MEDIUM
AV:N/AC:L/Au:S/C:P/I:N/A:N
RedHat/V2
RedHat/V3
Ubuntu

A vulnerability has been identified in SIMATIC PCS 7 V8.2 (All versions), SIMATIC PCS 7 V9.0 (All versions), SIMATIC PCS 7 V9.1 (All versions < V9.1 SP1), SIMATIC WinCC V15 and earlier (All versions < V15 SP1 Update 7), SIMATIC WinCC V16 (All versions < V16 Update 5), SIMATIC WinCC V17 (All versions < V17 Update 2), SIMATIC WinCC V7.4 (All versions < V7.4 SP1 Update 19), SIMATIC WinCC V7.5 (All versions < V7.5 SP2 Update 6). The password hash of a local user account in the remote server could be granted via public API to a user on the affected system. An authenticated attacker could brute force the password hash and use it to login to the server.

Weakness

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

Affected Software

Name Vendor Start Version End Version
Simatic_pcs_7 Siemens * 8.2 (including)
Simatic_pcs_7 Siemens 9.0 (including) 9.0 (including)
Simatic_pcs_7 Siemens 9.1 (including) 9.1 (including)
Simatic_wincc Siemens * 7.4 (excluding)
Simatic_wincc Siemens 7.4 (including) 7.4 (including)
Simatic_wincc Siemens 7.4-sp1 (including) 7.4-sp1 (including)
Simatic_wincc Siemens 7.4-sp1_update1 (including) 7.4-sp1_update1 (including)
Simatic_wincc Siemens 7.4-sp1_update10 (including) 7.4-sp1_update10 (including)
Simatic_wincc Siemens 7.4-sp1_update11 (including) 7.4-sp1_update11 (including)
Simatic_wincc Siemens 7.4-sp1_update12 (including) 7.4-sp1_update12 (including)
Simatic_wincc Siemens 7.4-sp1_update13 (including) 7.4-sp1_update13 (including)
Simatic_wincc Siemens 7.4-sp1_update14 (including) 7.4-sp1_update14 (including)
Simatic_wincc Siemens 7.4-sp1_update15 (including) 7.4-sp1_update15 (including)
Simatic_wincc Siemens 7.4-sp1_update16 (including) 7.4-sp1_update16 (including)
Simatic_wincc Siemens 7.4-sp1_update17 (including) 7.4-sp1_update17 (including)
Simatic_wincc Siemens 7.4-sp1_update18 (including) 7.4-sp1_update18 (including)
Simatic_wincc Siemens 7.4-sp1_update2 (including) 7.4-sp1_update2 (including)
Simatic_wincc Siemens 7.4-sp1_update3 (including) 7.4-sp1_update3 (including)
Simatic_wincc Siemens 7.4-sp1_update4 (including) 7.4-sp1_update4 (including)
Simatic_wincc Siemens 7.4-sp1_update5 (including) 7.4-sp1_update5 (including)
Simatic_wincc Siemens 7.4-sp1_update6 (including) 7.4-sp1_update6 (including)
Simatic_wincc Siemens 7.4-sp1_update7 (including) 7.4-sp1_update7 (including)
Simatic_wincc Siemens 7.4-sp1_update8 (including) 7.4-sp1_update8 (including)
Simatic_wincc Siemens 7.4-sp1_update9 (including) 7.4-sp1_update9 (including)
Simatic_wincc Siemens 7.5 (including) 7.5 (including)
Simatic_wincc Siemens 7.5-sp1 (including) 7.5-sp1 (including)
Simatic_wincc Siemens 7.5-sp1_update1 (including) 7.5-sp1_update1 (including)
Simatic_wincc Siemens 7.5-sp1_update2 (including) 7.5-sp1_update2 (including)
Simatic_wincc Siemens 7.5-sp2 (including) 7.5-sp2 (including)
Simatic_wincc Siemens 7.5-sp2_update1 (including) 7.5-sp2_update1 (including)
Simatic_wincc Siemens 7.5-sp2_update2 (including) 7.5-sp2_update2 (including)
Simatic_wincc Siemens 7.5-sp2_update3 (including) 7.5-sp2_update3 (including)
Simatic_wincc Siemens 7.5-sp2_update4 (including) 7.5-sp2_update4 (including)
Simatic_wincc Siemens 7.5-sp2_update5 (including) 7.5-sp2_update5 (including)
Simatic_wincc Siemens 13 (including) 13 (including)
Simatic_wincc Siemens 13-sp1 (including) 13-sp1 (including)
Simatic_wincc Siemens 13-sp2 (including) 13-sp2 (including)
Simatic_wincc Siemens 14.0.1 (including) 14.0.1 (including)
Simatic_wincc Siemens 15 (including) 15 (including)
Simatic_wincc Siemens 15.1 (including) 15.1 (including)
Simatic_wincc Siemens 15.1-update_1 (including) 15.1-update_1 (including)
Simatic_wincc Siemens 15.1-update_2 (including) 15.1-update_2 (including)
Simatic_wincc Siemens 15.1-update_3 (including) 15.1-update_3 (including)
Simatic_wincc Siemens 15.1-update_4 (including) 15.1-update_4 (including)
Simatic_wincc Siemens 15.1-update_5 (including) 15.1-update_5 (including)
Simatic_wincc Siemens 15.1-update_6 (including) 15.1-update_6 (including)
Simatic_wincc Siemens 16 (including) 16 (including)
Simatic_wincc Siemens 16-update1 (including) 16-update1 (including)
Simatic_wincc Siemens 16-update2 (including) 16-update2 (including)
Simatic_wincc Siemens 16-update3 (including) 16-update3 (including)
Simatic_wincc Siemens 16-update4 (including) 16-update4 (including)
Simatic_wincc Siemens 17 (including) 17 (including)
Simatic_wincc Siemens 17-update1 (including) 17-update1 (including)

Extended Description

There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:

Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:

Information exposures can occur in different ways:

It is common practice to describe any loss of confidentiality as an “information exposure,” but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.

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