CVE-2025-68132
📋 TL;DR
This vulnerability in EVerest EV charging software allows attackers to crash the process by sending malformed SLIP frames via serial input. It affects systems using the DZG_GSH01 powermeter SLIP parser before version 2025.12.0. The out-of-bounds read occurs during CRC verification when insufficient bytes are present.
💻 Affected Systems
- EVerest EV charging software stack
📦 What is this software?
Everest by Linuxfoundation
⚠️ Risk & Real-World Impact
Worst Case
Complete denial of service for EV charging operations, potentially disrupting charging sessions and requiring manual restart of charging equipment.
Likely Case
Process crash requiring system restart, temporarily disabling charging functionality until service is restored.
If Mitigated
No impact if patched or if serial input is properly isolated from untrusted sources.
🎯 Exploit Status
Exploitation requires access to serial interface, which may require physical proximity or compromised network access to serial-over-IP converters.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 2025.12.0
Vendor Advisory: https://github.com/EVerest/everest-core/security/advisories/GHSA-79gc-m8w6-9hx5
Restart Required: Yes
Instructions:
1. Update EVerest to version 2025.12.0 or later. 2. Restart the EVerest service. 3. Verify the fix by checking version and monitoring for crashes.
🔧 Temporary Workarounds
Serial Access Restriction
allRestrict physical and network access to serial interfaces used by EVerest.
# Configure firewall rules to block unauthorized access to serial-over-IP ports
# Implement physical security controls for serial ports
Input Validation Enhancement
linuxAdd size checks before accessing vector elements in custom builds.
// Add: if (vec.size() < 2) return false; before vec[vec.size()-1] access
🧯 If You Can't Patch
- Isolate serial interfaces from untrusted networks using firewalls and VLAN segmentation.
- Implement monitoring for process crashes and automatic restart mechanisms to minimize downtime.
🔍 How to Verify
Check if Vulnerable:
Check EVerest version and review code for is_message_crc_correct function without size validation.Check Version:
everest --version or check package manager for everest-core versionVerify Fix Applied:
Confirm version is 2025.12.0+ and test with malformed SLIP frames to ensure no crashes occur.📡 Detection & Monitoring
Log Indicators:
- Process crash logs from EVerest service
- Segmentation fault errors in system logs
- Unexpected service restarts
Network Indicators:
- Unusual serial traffic patterns
- Malformed SLIP frames on serial interfaces
SIEM Query:
source="systemd" AND "everest" AND ("segmentation fault" OR "crash" OR "SIGSEGV")