| Article No° | Product Name | Affected Version(s) |
|---|---|---|
| 1139022 | CHARX SEC-3000 | <= 1.5.0 |
| 1139018 | CHARX SEC-3050 | <= 1.5.0 |
| 1139012 | CHARX SEC-3100 | <= 1.5.0 |
| 1138965 | CHARX SEC-3150 | <= 1.5.0 |
Multiple vulnerabilities have been discovered in the Firmware of CHARX SEC charge controllers. These vulnerabilities were discovered as part of a PWN2OWN competition initiated by Trend Micro Zero Day Initiative (ZDI).
An unauthenticated remote attacker can modify configurations to perform a remote code execution due to a missing authentication for a critical function.
An unauthenticated remote attacker can influence the communication due to the lack of encryption of sensitive data via a MITM. Charging is not affected.
An unauthenticated local attacker can perform a privilege escalation due to improper input validation in the OCPP agent service.
An improper input validation in the Qualcom plctool allows a local attacker with low privileges to gain root access by changing the ownership of specific files.
An unauthenticated remote attacker can DoS the control agent due to a out-of-bounds read which may prevent or disrupt the charging functionality.
An unauthenticated remote attacker can DoS a control agent due to access of a uninitialized pointer which may prevent or disrupt the charging functionality.
An unauthenticated remote attacker can write memory out of bounds due to improper input validation in the MQTT stack. The brute force attack is not always successful because of memory randomization.
An unauthenticated remote attacker can perform a command injection with limited privileges due to improper input validation.
An unauthenticated remote attacker can read memory out of bounds due to improper input validation in the MQTT stack. The brute force attack is not always successful because of memory randomization.
An unauthenticated remote attacker can upload a arbitrary script file due to improper input validation. The upload destination is fixed and is write only.
An unauthenticated remote attacker can perform a log injection due to improper input validation. Only a certain log file is affected.
An unauthenticated remote attacker can perform a remote code execution due to an origin validation error. The access is limited to the service user.
An unauthenticated remote attacker can gain service level privileges through an incomplete cleanup during service restart after a DoS.
CVE-2024-25994, CVE-2024-25996,CVE-2024-25997,CVE-2024-26000
These vulnerabilities can be exploited by a malicious attacker without local account to gain root privileges, which allows him to take over the device.
CVE-2024-26003
This vulnerability can be used by a malicious attacker without local account to perform remote code execution with the privileges of the ControllerAgent service.
Some of the Vulnerabilities represent a medium risk on their own, nevertheless chaining or combining these vulnerabilities can trigger an RCE that leads to the complete compromise of the device.
Mitigation
Phoenix Contact recommends operating network-capable devices in closed networks or protected with a suitable firewall. For detailed information on our recommendations for measures to protect network-capable devices, please refer to our application note.
Measures to protect network-capable devices with Ethernet connection
Remediation
Phoenix Contact strongly recommends updating to firmware version v1.5.1 or higher, which fixes these vulnerabilities.
CERT@VDE coordinated with PHOENIX CONTACT
These vulnerabilities were discovered as part of a PWN2OWN competition initiated by Trend Micro Zero Day Initiative (ZDI).
We kindly appreciate the coordinated disclosure of this vulnerabilities by ZDI and the finders: