CVE Vulnerabilities

CVE-2018-10612

Improper Access Control

Published: Jan 29, 2019 | Modified: Nov 21, 2024
CVSS 3.x
9.8
CRITICAL
Source:
NVD
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
10 HIGH
AV:N/AC:L/Au:N/C:C/I:C/A:C
RedHat/V2
RedHat/V3
Ubuntu

In 3S-Smart Software Solutions GmbH CODESYS Control V3 products prior to version 3.5.14.0, user access management and communication encryption is not enabled by default, which could allow an attacker access to the device and sensitive information, including user credentials.

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
Control_for_beaglebone_sl Codesys 3.0 (including) 3.5.14.0 (excluding)
Control_for_empc-a/imx6_sl Codesys 3.0 (including) 3.5.14.0 (excluding)
Control_for_iot2000_sl Codesys 3.0 (including) 3.5.14.0 (excluding)
Control_for_linux_sl Codesys 3.0 (including) 3.5.14.0 (excluding)
Control_for_pfc100_sl Codesys 3.0 (including) 3.5.14.0 (excluding)
Control_for_pfc200_sl Codesys 3.0 (including) 3.5.14.0 (excluding)
Control_for_raspberry_pi_sl Codesys 3.0 (including) 3.5.14.0 (excluding)
Control_rte_sl Codesys 3.0 (including) 3.5.14.0 (excluding)
Control_runtime_toolkit Codesys 3.0 (including) 3.5.14.0 (excluding)
Control_win_sl Codesys 3.0 (including) 3.5.14.0 (excluding)
Development_system_v3 Codesys 3.0 (including) 3.5.14.0 (excluding)
Hmi_sl Codesys 3.0 (including) 3.5.14.0 (excluding)

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