Executive Summary

This vulnerability involves WebSocket endpoints that lack proper authentication mechanisms. Because of this, attackers can impersonate charging stations without authorization by connecting to the OCPP WebSocket endpoint using a known or discovered charging station identifier.

Once connected, the attacker can issue or receive OCPP commands as if they were a legitimate charger, enabling unauthorized control and manipulation of data sent to the backend.

Useful 0 Not Useful 0

Impact Analysis

The vulnerability can lead to several serious impacts including privilege escalation and unauthorized control of charging infrastructure.

• Attackers can impersonate legitimate charging stations.
• Unauthorized manipulation and corruption of charging network data reported to the backend.
• Potential disruption or misuse of charging services.

Useful 0 Not Useful 0

Compliance Impact

I don't know

Useful 0 Not Useful 0

Detection Guidance

This vulnerability involves unauthenticated access to WebSocket endpoints used by charging stations, where attackers can impersonate stations by connecting with known or discovered identifiers. Detection would involve monitoring network traffic for unauthorized or suspicious WebSocket connections to the OCPP endpoint, especially those that do not follow expected authentication patterns.

Specific commands or tools to detect this vulnerability are not provided in the available resources.

Useful 0 Not Useful 0

Mitigation Strategies

The vulnerability arises because WebSocket endpoints lack proper authentication, allowing unauthorized access and control. Immediate mitigation steps would logically include implementing authentication mechanisms on the WebSocket endpoints to ensure only legitimate charging stations can connect.

No explicit mitigation steps or recommendations are provided in the available resources.

Useful 0 Not Useful 0