CVE-2024-29212 json
Due to an unsafe de-serialization method used by the Veeam Service Provider Console(VSPC) server in communication between the management ag…
published 2y ago modified 4mo ago also EUVD-2024-26229
- cvss
- 9.9
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 75%
- public exploits
- 0
- none known
Summary
Due to an unsafe de-serialization method used by the Veeam Service Provider Console(VSPC) server in communication between the management agent and its components, under certain conditions, it is possible to perform Remote Code Execution (RCE) on the VSPC server machine.
Patch / fix
- veeam veeam_service_provider_console 7.0.0.19551, 8.0.0.19552
Is CVE-2024-29212 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
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2y ago
Exploit prediction
1.55% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 9.9 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
Affected products
- Veeam Service Provider Console
- veeam service_provider_console
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
References
-
veeam.com
/kb4575
vendor-advisory
Sources
- CVE List CVE-2024-29212
- NVD CVE-2024-29212
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.