In EVerest, by default, the EV is responsible for closing the connection if the module encounters an error during request processing
Description
EVerest is an EV charging software stack. In all versions up to and including 2025.12.1, the default value for terminate_connection_on_failed_response is False, which leaves the responsibility for session and connection termination to the EV. In this configuration, any errors encountered by the module are logged but do not trigger countermeasures such as session and connection reset or termination. This could be abused by a malicious user in order to exploit other weaknesses or vulnerabilities. While the default will stay at the setting that is described as potentially problematic in this reported issue, a mitigation is available by changing the terminate_connection_on_failed_response setting to true. However this cannot be set to this value by default since it can trigger errors in vehicle ECUs requiring ECU resets and lengthy unavailability in charging for vehicles. The maintainers judge this to be a much more important workaround then short-term unavailability of an EVSE, therefore this setting will stay at the current value.
Affected products
1- Range: 2022.12.0, 2022.12.1, 2023.1.0, …
Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
1- github.com/EVerest/everest-core/security/advisories/GHSA-wqh4-pj54-6xv9mitrex_refsource_CONFIRM
News mentions
0No linked articles in our index yet.