CVE-2025-5830

8.8 HIGH

📋 TL;DR

This vulnerability allows network-adjacent attackers to execute arbitrary code on Autel MaxiCharger AC Wallbox Commercial EV chargers without authentication. The heap-based buffer overflow in DLB_SlaveRegister message handling enables remote code execution on affected devices. EV charging station operators and facilities using these chargers are at risk.

💻 Affected Systems

Products:
  • Autel MaxiCharger AC Wallbox Commercial EV Chargers
Versions: Specific versions not publicly detailed in advisory
Operating Systems: Embedded firmware
Default Config Vulnerable: ⚠️ Yes
Notes: All network-connected installations are vulnerable by default. Authentication is not required for exploitation.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete compromise of EV charging infrastructure allowing attackers to disrupt charging operations, manipulate billing data, pivot to internal networks, or cause physical damage to vehicles/equipment.

🟠

Likely Case

Attackers gain control of charging stations to disrupt operations, steal electricity, or use as foothold for further network attacks.

🟢

If Mitigated

Isolated charging network segments prevent lateral movement, limiting impact to charging availability disruption.

🌐 Internet-Facing: HIGH
🏢 Internal Only: HIGH

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

No authentication required and network-adjacent access makes exploitation straightforward for skilled attackers.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Not specified in public advisory

Vendor Advisory: https://www.zerodayinitiative.com/advisories/ZDI-25-349/

Restart Required: Yes

Instructions:

1. Contact Autel for firmware update 2. Download latest firmware from Autel portal 3. Apply update via management interface 4. Reboot charger to activate patch

🔧 Temporary Workarounds

Network Segmentation

all

Isolate EV charging network from critical infrastructure and internet

Access Control Lists

all

Restrict network access to chargers from authorized management systems only

🧯 If You Can't Patch

  • Physically disconnect chargers from network and use local management only
  • Implement strict firewall rules allowing only essential traffic to/from chargers

🔍 How to Verify

Check if Vulnerable:

Check firmware version against vendor's patched version list. If unable to verify, assume vulnerable.

Check Version:

Check via charger's web interface or management system for firmware version

Verify Fix Applied:

Confirm firmware version matches or exceeds vendor's patched version. Test connectivity to verify functionality.

📡 Detection & Monitoring

Log Indicators:

  • Unusual network traffic to chargers
  • Multiple failed connection attempts
  • Unexpected firmware modification alerts

Network Indicators:

  • Unusual DLB_SlaveRegister message patterns
  • Traffic from unexpected sources to charger ports
  • Abnormal protocol behavior

SIEM Query:

source_ip NOT IN (authorized_management_ips) AND dest_port IN (charger_ports) AND protocol='DLB'

🔗 References

📤 Share & Export