EVerest affected by memory exhaustion in libocpp
Key facts
- Attack vector
- Adjacent network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- None · None · Low
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-770.
Summary
EVerest is an EV charging software stack, and EVerest libocpp is a C++ implementation of the Open Charge Point Protocol. In libocpp prior to version 0.30.1, pointers returned by the `strdup` calls are never freed. At each connection attempt, the newly allocated memory area will be leaked, potentially causing memory exhaustion and denial of service. Version 0.30.1 fixes the issue.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2025-68138
References
More EVerest vulnerabilities
- TI-2026-25456 EVerest: MQTT Switch-Phases Command Data Race Causing Charger State Corruptio CVSS 3.1HIGH 8.2
- TI-2024-24822 EVerest has an integer overflow in the "v2g_incoming_v2gtp" function CVSS 3.1CRITICAL 9.1
- TI-2026-18308 EVerest's unchecked SLAC payload length causes stack overflow in HomeplugMessage::setup_payload CVSS 3.1HIGH 8.8
- TI-2026-19334 EVerest has stack buffer overflow in ifreq.ifr_name when interface name exceeds IFNAMSIZ CVSS 3.1HIGH 8.4
- TI-2026-18154 EVerest has off-by-one stack buffer overflow in IsoMux certificate filename parsing CVSS 3.1HIGH 8.4
- TI-2025-41718 EVerest's Integer Overflow and Signed to Unsigned conversion lead to either stack buffer overflow or infinite loop CVSS 3.1HIGH 8.4
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences