Authentication bypass & Remote code execution in Schneider Electric EVlink Charging Stations


Authentication bypass & Remote code execution


Multiple Schneider Electric EVlink Charging Stations

Vulnerable Version

Firmware R7 (Version V3.3.0.15)

Fixed Version

Firmware R8 (Version V3.4.0.1)

CVE Number

CVE-2021-22707, CVE-2021-22708






Stefan Viehböck (Office Vienna)

The Schneider Electric electric car charging stations product line "EVlink" is affected by two vulnerabilities that allow a remote attacker to execute arbitrary commands on the system. Attackers can change the charging station configuration arbitrarily, charge without authorization or send arbitrary charging data records to the supervision system (e.g. overcharging/undercharging). Furthermore the attackers can gain persistent access to the charging station operating system and use this access for further attacks within the target network.

Vendor description

"Our mission is to be your digital partner for Sustainability and Efficiency. We drive digital transformation by integrating world-leading process and energy technologies, end-point to cloud connecting products, controls, software and services, across the entire lifecycle, enabling integrated company management, for homes, buildings, data centers, infrastructure and industries. We are the most local of global companies. We are advocates of open standards and partnership ecosystems that are passionate about our shared Meaningful Purpose, Inclusive and Empowered values."



Business recommendation

The vendor provides a firmware update for the affected charging stations which should be installed immediately. SEC Consult highly recommends to perform a thorough security review of the Schneider Electric EVlink product line conducted by security professionals to identify and resolve potential further security issues.


Vulnerability overview/description

1) Authentication Bypass with Undocumented Hard Coded Credentials (CVE-2021-22707)

The authentication for the EVlink administration web interface can be bypassed with undocumented and hard coded HTTP cookie values. Initial analysis indicates that this authentication method is intended for local authentication by the "evse" service.

2) Lack of Secure Update Mechanism / Remote Code Execution (CVE-2021-22708)

An authenticated attacker can upload arbitrary, malicious firmware updates to the device and thus gain remote code execution. The firmware integrity is checked by generating a SHA256 hash of the firmware update contents and a hard coded value and comparing it against a hash stored within the firmware update (CONTROL file).

An attacker can create a malicious firmware update by modifying the firmware contents and adjusting the hash in the CONTROL file.

Based on public information we believe this vulnerability type was once reported as CVE-2018-7801 by Positive Technologies before. The patch notes [1] indicate that a signature was introduced in R6 software v3.2.0-12 as a fix. It is likely this fix did not actually fix the vulnerability.



Proof of concept

1) Authentication Bypass with Undocumented Hard Coded Credentials (CVE-2021-22707)

The web interface authentication can be bypassed by setting the following HTTP cookie values:

  • CURLTOKEN=b35fcdc1ea1221e6dd126e172a0131c5a
  • SESSIONID=admin

With those cookies the attacker is logged in with admin permissions.

2) Lack of Secure Update Mechanism / Remote Code Execution (CVE-2021-22708)

The file "" stored in /mnt/datas/opt/evse/ performs the validation of the firmware update image.

Below is an excerpt:


# extract files from archive (epz is an epk.gz, but tar xf will handle it)
tar xf "$file"

if [[ ! -f CONTROL ]]; then
abort "KO, missing signature"

echo $private_key > private

find . -type f | grep -v CONTROL | xargs sha256sum | awk '{print $1}' | sort | sha256sum > ../CONTROL2
mv ../CONTROL2 .
rm private

if [[ "`diff CONTROL CONTROL2`" != "" ]]; then
abort "KO, signatures mismatch"

The $private_key parameter is not a cryptographic signature. It is a hard coded key found in the "cgiServer" and "evse" binary and not a cryptographic signature.

The value is:


It is placed in the firmware directory during the computation of the SHA256 hash. This script can be modified easily to provide a valid hash for the CONTROL file.


Vulnerable / tested versions

The vulnerabilities have been found in the firmware R7 (Version V3.3.0.15), which is the latest version at the time of discovery.

Initial analysis indicates that at least the following Schneider Electric products are affected:

  • EVlink Charging Smart Wallbox
  • EVlink Parking
  • EVlink City ranges


Vendor contact timeline


2021-03-11 Contacting vendor through
2021-03-11 Vendor response, vulnerabilities are under investigation.
2021-03-11 Vendor response, vulnerabilities confirmed, fix and disclosure scheduled for July 2021.
2021-07-14 Coordinated release of security advisory.


Update to the most recent firmware version provided on the vendor's website.

Version R8 V3.4.0.1 includes a fix for the vulnerabilities.

Further information can be found in the Schneider Electric security notification:





EOF Stefan Viehböck / @2021


Interested to work with the experts of SEC Consult? Send us your application.

Interested in improving your cyber security with the experts of SEC Consult? Contact our local offices.