CVE-2024-37310 json
EVerest has an integer overflow in the "v2g_incoming_v2gtp" function
published 2y ago modified 4mo ago also EUVD-2024-36981
- cvss
- 9.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 52%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- EVerest everest-core 2024.6.0
Is CVE-2024-37310 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 2y ago
Exploit prediction
0.67% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H |
Affected products
- EVerest everest-core
Classification
References
- github.com /EVerest/everest-core/commit/f73620c4c0f626e1097068a47e10cc27b369ad8e
- github.com /EVerest/everest-core/security/advisories/GHSA-8g9q-7qr9-vc96
- github.com /EVerest/everest-core/releases/tag/2024.3.1
- github.com /EVerest/everest-core/releases/tag/2024.6.0
- plaxidityx.com /blog/automotive-cyber-security/ev-cyber-security-plaxidityx-discovers-critical-vulnerability-in-everest-open-
Sources
- CVE List CVE-2024-37310
- NVD CVE-2024-37310
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.