CVE-2024-11666
📋 TL;DR
This vulnerability allows remote unauthenticated attackers positioned between EV chargers and eCharge cloud infrastructure to execute arbitrary commands with elevated privileges on affected devices. The issue stems from disabled peer verification in cloud communication channels. This affects EV charging stations running vulnerable eCharge firmware versions.
💻 Affected Systems
- eCharge EV charging controllers
📦 What is this software?
⚠️ Risk & Real-World Impact
Worst Case
Complete compromise of EV charging infrastructure allowing attackers to disable charging, manipulate billing, cause electrical damage, or use devices as network footholds.
Likely Case
Attackers intercepting communications to execute commands that disrupt charging operations, steal user data, or manipulate charging parameters.
If Mitigated
Limited impact if network segmentation isolates chargers and proper TLS verification is enforced.
🎯 Exploit Status
Exploitation requires network positioning between device and cloud, but no authentication or special tools needed.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Unknown
Vendor Advisory: Not available
Restart Required: Yes
Instructions:
1. Contact eCharge vendor for patched firmware
2. Backup configuration
3. Apply firmware update
4. Verify TLS/SSL peer verification is enabled
🔧 Temporary Workarounds
Network segmentation
allIsolate EV charging controllers from untrusted networks
TLS enforcement
allConfigure network devices to enforce TLS with certificate validation
🧯 If You Can't Patch
- Segment charging network completely from other corporate networks
- Implement strict firewall rules allowing only necessary cloud communications with certificate pinning
🔍 How to Verify
Check if Vulnerable:
Check firmware version on charging controller via management interfaceCheck Version:
Device-specific command via management interfaceVerify Fix Applied:
Verify firmware version is above 2.0.4 and test TLS handshake with certificate validation📡 Detection & Monitoring
Log Indicators:
- Unexpected command execution logs
- Failed TLS handshake attempts
- Unusual cloud communication patterns
Network Indicators:
- Unencrypted or improperly authenticated cloud communications
- MITM attack patterns between charger and cloud
SIEM Query:
Search for failed TLS certificate validation events from charging controller IPs