CVE Vulnerabilities

CVE-2019-9008

Incorrect Permission Assignment for Critical Resource

Published: Sep 17, 2019 | Modified: Mar 29, 2023
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
6.5 MEDIUM
AV:N/AC:L/Au:S/C:P/I:P/A:P
RedHat/V2
RedHat/V3
Ubuntu

An issue was discovered in 3S-Smart CODESYS V3 through 3.5.12.30. A user with low privileges can take full control over the runtime.

Weakness

The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.

Affected Software

Name Vendor Start Version End Version
Control_for_beaglebone Codesys * 3.5.13.0 (excluding)
Control_for_empc-a/imx6 Codesys * 3.5.13.0 (excluding)
Control_for_iot2000 Codesys * 3.5.13.0 (excluding)
Control_for_pfc100 Codesys * 3.5.13.0 (excluding)
Control_for_pfc200 Codesys * 3.5.13.0 (excluding)
Control_for_raspberry_pi Codesys * 3.5.13.0 (excluding)
Control_rte Codesys * 3.5.13.0 (excluding)
Control_win Codesys * 3.5.13.0 (excluding)
Hmi Codesys * 3.5.13.0 (excluding)
Simulation_runtime Codesys * 3.5.13.0 (excluding)

Potential Mitigations

  • Run the code in a “jail” or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.
  • OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For example, java.io.FilePermission in the Java SecurityManager allows the software to specify restrictions on file operations.
  • This may not be a feasible solution, and it only limits the impact to the operating system; the rest of the application may still be subject to compromise.
  • Be careful to avoid CWE-243 and other weaknesses related to jails.

References