A CWE-259: Use of Hard-coded Password vulnerability exists in EVlink City (EVC1S22P4 / EVC1S7P4 all versions prior to R8 V3.4.0.1), EVlink Parking (EVW2 / EVF2 / EV.2 all versions prior to R8 V3.4.0.1), and EVlink Smart Wallbox (EVB1A all versions prior to R8 V3.4.0.1 ) that could allow an attacker to gain unauthorized administrative privileges when accessing to the charging station web server.
Weakness
The product contains a hard-coded password, which it uses for its own inbound authentication or for outbound communication to external components.
Affected Software
Name |
Vendor |
Start Version |
End Version |
Evlink_city_evc1s22p4_firmware |
Schneider-electric |
* |
r8_v3.4.0.1 (excluding) |
Extended Description
There are two main variations of a hard-coded password:
Potential Mitigations
- For inbound authentication: apply strong one-way hashes to your passwords and store those hashes in a configuration file or database with appropriate access control. That way, theft of the file/database still requires the attacker to try to crack the password. When receiving an incoming password during authentication, take the hash of the password and compare it to the hash that you have saved.
- Use randomly assigned salts for each separate hash that you generate. This increases the amount of computation that an attacker needs to conduct a brute-force attack, possibly limiting the effectiveness of the rainbow table method.
- For front-end to back-end connections: Three solutions are possible, although none are complete.
References