In Bender/ebee Charge Controllers in multiple versions are prone to Hardcoded Credentials. Bender charge controller CC612 in version 5.20.1 and below is prone to hardcoded ssh credentials. An attacker may use the password to gain administrative access to the web-UI.
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 |
| Cc612_firmware |
Bender |
5.11.0 (including) |
5.11.2 (excluding) |
| Cc612_firmware |
Bender |
5.12.0 (including) |
5.12.5 (excluding) |
| Cc612_firmware |
Bender |
5.13.0 (including) |
5.13.2 (excluding) |
| Cc612_firmware |
Bender |
5.20.0 (including) |
5.20.2 (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