CVE-2025-68137: CWE-120: Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') in EVerest everest-core
CVE-2025-68137 is a high-severity buffer overflow vulnerability in the EVerest everest-core EV charging software stack versions prior to 2025. 10. 0. It arises from an integer overflow in the SdpPacket::parse_header() function, causing incorrect buffer length calculations that lead to either an infinite loop or a stack buffer overflow depending on the server configuration (TCP or TLS). This vulnerability can result in full compromise of confidentiality, integrity, and availability without requiring authentication or user interaction. The flaw is fixed in version 2025. 10. 0. European organizations operating EV charging infrastructure using affected versions are at risk of service disruption and potential remote code execution. Mitigation requires immediate upgrade to the patched version and careful network segmentation of EV charging systems.
AI Analysis
Technical Summary
CVE-2025-68137 is a classic buffer overflow vulnerability classified under CWE-120 and related to CWE-835 (loop with unreachable exit condition) found in the EVerest everest-core software stack used for managing electric vehicle (EV) charging stations. The vulnerability stems from an integer overflow in the SdpPacket::parse_header() function. Specifically, after reading a complete header of size 8 bytes, the current buffer length is incorrectly set to 7. When calculating the remaining length to read, the code subtracts the header length from the current length, resulting in a negative value. Because the length is stored in an unsigned size_t type, this negative value is interpreted as a very large positive number (SIZE_MAX or slightly less). This causes the software to either enter an infinite loop (in plain TCP servers) or trigger a stack buffer overflow (in TLS servers). The buffer overflow can lead to memory corruption, potentially allowing remote attackers to execute arbitrary code, crash the service, or cause denial of service. The vulnerability does not require authentication or user interaction, increasing its risk. The issue was resolved in version 2025.10.0 of everest-core. No known exploits are reported in the wild yet, but the high CVSS score of 8.4 reflects the critical impact and complexity of exploitation due to the high attack complexity and network attack vector. The vulnerability affects all versions prior to 2025.10.0.
Potential Impact
For European organizations, this vulnerability poses a significant threat to the security and availability of EV charging infrastructure, which is critical for the growing electric vehicle market and sustainable transportation goals. Exploitation could lead to remote code execution, allowing attackers to take control of charging stations or backend management systems, potentially disrupting EV charging services across wide areas. This disruption could impact consumer trust, cause financial losses, and affect critical infrastructure reliant on EV fleets. Confidentiality breaches could expose sensitive operational data or user information. The infinite loop scenario could cause denial of service, degrading the availability of charging stations. Given the increasing adoption of EVs in Europe and the strategic importance of clean energy infrastructure, this vulnerability could be leveraged by threat actors aiming to cause economic or reputational damage. The lack of authentication requirements makes it easier for attackers to exploit the flaw remotely, increasing the urgency for mitigation.
Mitigation Recommendations
European organizations should immediately upgrade all instances of everest-core to version 2025.10.0 or later to eliminate the vulnerability. Until upgrades are completed, network segmentation should be enforced to isolate EV charging infrastructure from broader enterprise networks and the internet, reducing exposure. Implement strict firewall rules to limit access to the affected services only to trusted management systems. Monitor network traffic for unusual patterns indicative of exploitation attempts, such as repeated malformed SDP packets or anomalous connection behaviors. Conduct thorough code audits and penetration testing on EV charging software stacks to identify similar vulnerabilities. Establish incident response plans specifically addressing EV infrastructure compromise. Collaborate with vendors to ensure timely patch deployment and receive security advisories. Finally, consider deploying runtime protections such as stack canaries and address space layout randomization (ASLR) if supported by the platform to mitigate exploitation impact.
Affected Countries
Germany, France, Netherlands, Norway, Sweden, United Kingdom
CVE-2025-68137: CWE-120: Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') in EVerest everest-core
Description
CVE-2025-68137 is a high-severity buffer overflow vulnerability in the EVerest everest-core EV charging software stack versions prior to 2025. 10. 0. It arises from an integer overflow in the SdpPacket::parse_header() function, causing incorrect buffer length calculations that lead to either an infinite loop or a stack buffer overflow depending on the server configuration (TCP or TLS). This vulnerability can result in full compromise of confidentiality, integrity, and availability without requiring authentication or user interaction. The flaw is fixed in version 2025. 10. 0. European organizations operating EV charging infrastructure using affected versions are at risk of service disruption and potential remote code execution. Mitigation requires immediate upgrade to the patched version and careful network segmentation of EV charging systems.
AI-Powered Analysis
Technical Analysis
CVE-2025-68137 is a classic buffer overflow vulnerability classified under CWE-120 and related to CWE-835 (loop with unreachable exit condition) found in the EVerest everest-core software stack used for managing electric vehicle (EV) charging stations. The vulnerability stems from an integer overflow in the SdpPacket::parse_header() function. Specifically, after reading a complete header of size 8 bytes, the current buffer length is incorrectly set to 7. When calculating the remaining length to read, the code subtracts the header length from the current length, resulting in a negative value. Because the length is stored in an unsigned size_t type, this negative value is interpreted as a very large positive number (SIZE_MAX or slightly less). This causes the software to either enter an infinite loop (in plain TCP servers) or trigger a stack buffer overflow (in TLS servers). The buffer overflow can lead to memory corruption, potentially allowing remote attackers to execute arbitrary code, crash the service, or cause denial of service. The vulnerability does not require authentication or user interaction, increasing its risk. The issue was resolved in version 2025.10.0 of everest-core. No known exploits are reported in the wild yet, but the high CVSS score of 8.4 reflects the critical impact and complexity of exploitation due to the high attack complexity and network attack vector. The vulnerability affects all versions prior to 2025.10.0.
Potential Impact
For European organizations, this vulnerability poses a significant threat to the security and availability of EV charging infrastructure, which is critical for the growing electric vehicle market and sustainable transportation goals. Exploitation could lead to remote code execution, allowing attackers to take control of charging stations or backend management systems, potentially disrupting EV charging services across wide areas. This disruption could impact consumer trust, cause financial losses, and affect critical infrastructure reliant on EV fleets. Confidentiality breaches could expose sensitive operational data or user information. The infinite loop scenario could cause denial of service, degrading the availability of charging stations. Given the increasing adoption of EVs in Europe and the strategic importance of clean energy infrastructure, this vulnerability could be leveraged by threat actors aiming to cause economic or reputational damage. The lack of authentication requirements makes it easier for attackers to exploit the flaw remotely, increasing the urgency for mitigation.
Mitigation Recommendations
European organizations should immediately upgrade all instances of everest-core to version 2025.10.0 or later to eliminate the vulnerability. Until upgrades are completed, network segmentation should be enforced to isolate EV charging infrastructure from broader enterprise networks and the internet, reducing exposure. Implement strict firewall rules to limit access to the affected services only to trusted management systems. Monitor network traffic for unusual patterns indicative of exploitation attempts, such as repeated malformed SDP packets or anomalous connection behaviors. Conduct thorough code audits and penetration testing on EV charging software stacks to identify similar vulnerabilities. Establish incident response plans specifically addressing EV infrastructure compromise. Collaborate with vendors to ensure timely patch deployment and receive security advisories. Finally, consider deploying runtime protections such as stack canaries and address space layout randomization (ASLR) if supported by the platform to mitigate exploitation impact.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2025-12-15T18:09:12.694Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69712a9c4623b1157ce7dac5
Added to database: 1/21/2026, 7:35:56 PM
Last enriched: 1/28/2026, 8:23:44 PM
Last updated: 2/7/2026, 2:47:13 PM
Views: 70
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-2088: SQL Injection in PHPGurukul Beauty Parlour Management System
MediumCVE-2026-2087: SQL Injection in SourceCodester Online Class Record System
MediumCVE-2026-2086: Buffer Overflow in UTT HiPER 810G
HighCVE-2026-2085: Command Injection in D-Link DWR-M921
HighCVE-2026-2084: OS Command Injection in D-Link DIR-823X
HighActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.