Schneider Electric has a recommendation and an update to handle use of hard-coded credentials, code injection, and SQL injection vulnerabilities in its EVLink Parking, according to a report with NCCIC.
Successful exploitation of these remotely exploitable vulnerabilities could allow an attacker to stop the device and prevent charging, execute arbitrary commands, and access the web interface with full privileges.
An electric vehicle charging station, EVLink Parking Versions 3.2.0-12_v1 and prior suffer from the issues, discovered by Vladimir Kononovich and Vyacheslav Moskvin of Positive Technologies.
A hard-coded credentials vulnerability exists that could enable an attacker to gain access to the device.
CVE-2018-7800 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 9.8 .
In addition, a code injection vulnerability exists that could allow remote code execution with maximum privileges.
CVE-2018-7801 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 8.8.
Also, a SQL injection vulnerability exists that could give an attacker access to the web interface with full privileges.
CVE-2018-7802 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 6.4.
The product sees use mainly in the transportation sector. It also sees action on a global basis.
No known public exploits specifically target these vulnerabilities. However, an attacker with low skill level could leverage the vulnerabilities.
Schneider Electric recommends users setup a firewall to restrict remote access to the charging stations by unauthorized users. A software update is also available for download to mitigate these vulnerabilities.
For more information see Schneider Electric’s security notification.
Schneider Electric also recommends the following cybersecurity best practices:
• Locate control and safety system networks and remote devices behind firewalls, and isolate them from the business network.
• Physical controls should be in place so that no unauthorized person would have access to the ICS and safety controllers, peripheral equipment or the ICS and safety networks.
• All controllers should reside in locked cabinets and never be left in the “Program” mode.
• All programming software should be kept in locked cabinets and should never be connected to any network other than the network for the devices that it is intended.
• All methods of mobile data exchange with the isolated network such as CDs, USB drives, etc. should be scanned before use in the terminals or any node connected to these networks.
• Laptops that have connected to any other network besides the intended network should never be allowed to connect to the safety or control networks without proper sanitation.
• Minimize network exposure for all control system devices and/or systems, and ensure they are not accessible from the Internet.
• When remote access is required, use secure methods, such as virtual private networks (VPNs), recognizing that VPNs may have vulnerabilities and should be updated to the most current version available. Also recognize that VPN is only as secure as the connected devices.