charx_sec_3150 vulnerabilities
8 known vulnerabilities in charx_sec_3150 from Phoenixcontact. 8 are rated high or critical. Each entry lists the affected versions and the release that fixes it, where the vendor has published one.
Latest first
- 9.8 Critical severity
CHARX SEC-3000: Use of Default Credentials
A remote unauthenticated attacker can use the firmware update feature on the LAN interface of the device to reset the password for the predefined, low-privileged user “user-app” to the default password.
- 7.8 High severity
CHARX SEC-3000: Improper Neutralization of Special Elements used in a Command
A local attacker with low privileges can use a command injection vulnerability to gain root privileges due to improper input validation using the OCPP Remote service.
- 7.0 High severity
CHARX SEC-3000: Cleartext Transmission of Sensitive Information
An unauthenticated remote attacker can extract a session token with a MitM attack and gain web-based management access with the privileges of the currently logged in user due to cleartext transmission of sensitive information. No additional user interaction is
- 8.7 High severity
CHARX SEC-3000: Cleartext Transmission of Sensitive Information
An unauthenticated remote attacker can influence the communication due to the lack of encryption of sensitive data via a MITM. Charging is not affected.
- 7.5 High severity
CHARX SEC-3000: Access of Uninitialized Pointer
An unauthenticated remote attacker can DoS a control agent due to access of a uninitialized pointer which may prevent or disrupt the charging functionality.
- 7.8 High severity
An improper input validation in the Qualcom plctool allows a local attacker with low…
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.
- 9.8 Critical severity
CHARX SEC-3000: Out-of-bounds Write
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.
- 9.8 Critical severity
An unauthenticated remote attacker can modify configurations to perform a remote code…
An unauthenticated remote attacker can modify configurations to perform a remote code execution, gain root rights or perform an DoS due to improper input validation.