Missing authentication in OCPP WebSocket endpoints enables unauthenticated attackers to impersonate charging stations, leading to unauthorized infrastructure control and data corruption.

This vulnerability involves a total lack of authentication on WebSocket endpoints used for the Open Charge Point Protocol (OCPP). An unauthenticated attacker can establish a connection using a valid station ID, allowing them to intercept or inject charging commands and manipulate the backend's view of the network status.

The impact is critical, as evidenced by the CVSS score of 9.4, involving potential privilege escalation and unauthorized control over EV charging hardware. Successful exploitation could lead to revenue loss, incorrect billing, and significant reputational damage if the charging network is compromised or rendered inoperable.

Immediate Action: Apply the latest security updates provided by the vendor to enforce authentication on all WebSocket communication channels.

Proactive Monitoring: Implement logging for all WebSocket connection attempts and set up alerts for any connection requests that do not provide valid, pre-shared credentials.

Compensating Controls: Utilize a Web Application Firewall (WAF) capable of inspecting WebSocket traffic or place the management backend behind a secure gateway that requires mutual TLS (mTLS) for all station connections.

Public Exploit Available: false

Immediate action is required to secure the charging infrastructure. Security teams should verify that all endpoints require robust authentication and that no "default" or "test" endpoints remain exposed to the public internet.