CVE-2025-5827
📋 TL;DR
A stack-based buffer overflow in the ble_process_esp32_msg function of Autel MaxiCharger AC Wallbox Commercial EV chargers allows network-adjacent attackers to execute arbitrary code without authentication. This vulnerability affects EV charging stations that use the vulnerable firmware. Attackers can gain full control of the charger device.
💻 Affected Systems
- Autel MaxiCharger AC Wallbox Commercial EV Charger
📦 What is this software?
Maxicharger Ac Elite Business C50 Firmware by Autel
View all CVEs affecting Maxicharger Ac Elite Business C50 Firmware →
Maxicharger Ac Elite Business C50 Firmware by Autel
View all CVEs affecting Maxicharger Ac Elite Business C50 Firmware →
Maxicharger Dc Compact Mobile Firmware by Autel
View all CVEs affecting Maxicharger Dc Compact Mobile Firmware →
Maxicharger Dc Compact Mobile Firmware by Autel
View all CVEs affecting Maxicharger Dc Compact Mobile Firmware →
Maxicharger Dc Compact Pedestal Firmware by Autel
View all CVEs affecting Maxicharger Dc Compact Pedestal Firmware →
Maxicharger Dc Compact Pedestal Firmware by Autel
View all CVEs affecting Maxicharger Dc Compact Pedestal Firmware →
⚠️ Risk & Real-World Impact
Worst Case
Complete device takeover allowing attackers to disable charging, manipulate billing, access connected vehicle data, or use the device as a foothold into the network.
Likely Case
Device compromise leading to service disruption, unauthorized access to charging functions, or data exfiltration from the device.
If Mitigated
Limited impact if network segmentation prevents adjacent access, but device remains vulnerable to local attackers.
🎯 Exploit Status
Exploitation requires network adjacency (Bluetooth range) and knowledge of the BLE communication protocol. No authentication is required.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Not specified
Vendor Advisory: Not provided in available references
Restart Required: Yes
Instructions:
1. Contact Autel for firmware update availability. 2. Download official firmware from Autel support. 3. Apply update following manufacturer instructions. 4. Verify successful update.
🔧 Temporary Workarounds
Disable BLE if not required
allTurn off Bluetooth Low Energy functionality if not needed for operations
Manufacturer-specific configuration command not publicly available
Network segmentation
allIsolate EV chargers on separate network segments with strict access controls
🧯 If You Can't Patch
- Physically restrict access to charging area to prevent Bluetooth proximity attacks
- Implement continuous monitoring for unusual BLE traffic patterns
🔍 How to Verify
Check if Vulnerable:
Check firmware version against vendor advisory when available. Currently, assume all devices are vulnerable until patched.
Check Version:
Manufacturer-specific command not publicly documented
Verify Fix Applied:
Verify firmware version matches patched version from vendor advisory
📡 Detection & Monitoring
Log Indicators:
- Unusual BLE connection attempts
- Firmware crash logs
- Unexpected device reboots
Network Indicators:
- Abnormal BLE traffic patterns
- Multiple failed BLE connection attempts from single source
SIEM Query:
Not applicable - embedded device logs typically not integrated into SIEM