Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2024-25999 Overview
CVE-2024-25999 is a privilege escalation vulnerability affecting Phoenix Contact CHARX SEC-3000, SEC-3050, SEC-3100, and SEC-3150 electric vehicle charging controllers. The flaw resides in the Open Charge Point Protocol (OCPP) agent service, which fails to properly validate input. A local attacker without authentication can leverage this weakness to escalate privileges on affected devices. The vulnerability is tracked under [CWE-20: Improper Input Validation] and impacts firmware across the entire CHARX SEC-3xxx product line used in electric vehicle supply equipment (EVSE) deployments.
Critical Impact
Successful exploitation grants an unauthenticated local attacker elevated privileges on the charging controller, enabling full compromise of confidentiality, integrity, and availability of the EV charging infrastructure.
Affected Products
- Phoenix Contact CHARX SEC-3000 and SEC-3000 firmware
- Phoenix Contact CHARX SEC-3050 and SEC-3050 firmware
- Phoenix Contact CHARX SEC-3100 / SEC-3150 and associated firmware
Discovery Timeline
- 2024-03-12 - CVE-2024-25999 published to the National Vulnerability Database
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2024-25999
Vulnerability Analysis
The vulnerability affects the OCPP agent service running on Phoenix Contact CHARX SEC charging controllers. OCPP is the standard application-layer protocol used between EV charging stations and central management systems. The agent service accepts input that is not sufficiently validated before being processed in a privileged execution context. An attacker with local access to the device can craft malicious input to the OCPP agent and escalate privileges beyond the attacker's initial authorization level. Because exploitation requires only local access and does not require user interaction, an attacker who has gained a low-privilege foothold on the device, such as through a lower-tier service or exposed interface, can obtain full control of the charging controller.
Root Cause
The root cause is improper input validation [CWE-20] within the OCPP agent service. The service does not adequately sanitize or constrain data received through its processing paths before acting on it with elevated privileges. This allows attacker-controlled input to influence privileged operations.
Attack Vector
The attack vector is local. The attacker needs code execution or shell access on the device, but no authentication to the OCPP agent itself is required. The attacker interacts with the vulnerable agent service and supplies malformed or unexpected input that triggers the validation flaw, resulting in privilege escalation to the context under which the OCPP agent runs.
No verified public exploit code is available for CVE-2024-25999. For protocol-level technical details, refer to the VDE Security Advisory VDE-2024-011.
Detection Methods for CVE-2024-25999
Indicators of Compromise
- Unexpected processes spawned by the OCPP agent service outside of normal charging workflow operations.
- Shell or interpreter processes with parent lineage tied to the OCPP agent binary on CHARX SEC devices.
- Modifications to privileged configuration files or system binaries following inbound traffic to the OCPP service port.
- Anomalous OCPP messages containing malformed fields, oversized values, or unexpected control characters.
Detection Strategies
- Monitor process execution trees on CHARX SEC firmware for the OCPP agent spawning unexpected child processes.
- Baseline normal OCPP message structures and alert on deviations in field length, encoding, or type.
- Correlate local login or service access events with subsequent privilege-level changes on the device.
Monitoring Recommendations
- Forward CHARX SEC syslog output to a central logging platform for review of authentication and service events.
- Capture and inspect network traffic between charge points and management systems for OCPP protocol anomalies.
- Alert on configuration file changes under directories owned by the OCPP agent service account.
How to Mitigate CVE-2024-25999
Immediate Actions Required
- Apply the firmware update published by Phoenix Contact as referenced in VDE-2024-011.
- Restrict physical and local network access to CHARX SEC charging controllers to authorized personnel only.
- Audit existing accounts and services on affected devices for signs of prior unauthorized privilege escalation.
Patch Information
Phoenix Contact has coordinated disclosure through CERT@VDE. Refer to VDE Security Advisory VDE-2024-011 for the list of fixed firmware versions and update procedures for each CHARX SEC-3xxx model.
Workarounds
- Place CHARX SEC devices on isolated management networks segmented from general IT and operational traffic.
- Enforce strong authentication and physical access controls on any system that can reach the OCPP agent service.
- Disable or restrict unused local services on the controller to reduce the attack surface available for initial foothold.
# Example: restrict management access to CHARX SEC devices with firewall rules
iptables -A INPUT -s <mgmt_subnet> -p tcp --dport <ocpp_port> -j ACCEPT
iptables -A INPUT -p tcp --dport <ocpp_port> -j DROP
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

