Martin Floeck

**Name of the Vulnerable Software and Affected Versions** SIMATIC CN 4100 versions prior to V3.0 **Description** A vulnerability has been identified in the SIMATIC CN 4100 device, which contains undocumented users and credentials. This issue is related to the use of pre-installed credentials. An attacker could misuse these credentials to compromise the device locally or over the network, potentially allowing a remote attacker to gain full access to the device. **Recommendations** For versions prior to V3.0, update to version V3.0 or later to resolve the issue. As a temporary workaround, consider restricting network access to the device and changing any default or pre-installed credentials to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** SIMATIC CN 4100 versions prior to V3.0 **Description** A vulnerability has been identified in the SIMATIC CN 4100 device, where it contains a hard-coded password used for the privileged system user `root` and for the boot loader `GRUB` by default. This issue is related to the use of pre-installed credentials. If an attacker manages to crack the password hash, they can gain root access to the device, allowing for unauthorized access with root privileges. **Recommendations** For versions prior to V3.0, consider changing the default password for the `root` user and the `GRUB` boot loader to a strong, unique password to prevent unauthorized access. As a temporary workaround, restrict access to the device to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** SIMATIC CN 4100 versions prior to V3.0 **Description** The issue is related to the absence of an immutable root of trust in the device's firmware, which can be exploited through an unrestricted USB port. This could allow an attacker with local access to the device to gain complete read/write access to the filesystem by potentially booting another operating system. **Recommendations** For SIMATIC CN 4100 versions prior to V3.0, update to version V3.0 or later to resolve the issue. As a temporary workaround, consider restricting access to the USB port to minimize the risk of exploitation.