# CVE-2024-37310: EVerest has an integer overflow in the "v2g_incoming_v2gtp" function

> A remote attacker can trigger an integer overflow in EVerest EV charging software to corrupt the heap, potentially leading to code execution or denial of service.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2024
- **Updated:** 16 Dec 2024
- **Also known as:** GHSA-8g9q-7qr9-vc96

## What is CVE-2024-37310?

CVE-2024-37310 is a critical vulnerability in everest-core, published on 10 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-190 (Integer Overflow or Wraparound), CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2024-37310?


## How do I fix CVE-2024-37310?

No fix has been published for CVE-2024-37310 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-37310 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-37310 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-37310 and fix it if it is affected.

What it is: CVE-2024-37310 is a critical vulnerability in everest-core, published on 10 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-37310 exists.

Affected product: everest-core. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-37310/ (Markdown: https://insights.sbomify.com/CVE-2024-37310/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-37310
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-37310
- OSV: https://osv.dev/vulnerability/CVE-2024-37310

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-37310/
Summaries are generated and may contain mistakes; the official description above is the record.