Service Provider Console: Deserialization of Untrusted Data
CVE-2024-29212 is a critical-severity deserialization of untrusted data vulnerability in Service Provider Console from Veeam, with a CVSS 3.0 base score of 9.9 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. Affected Service Provider Console versions: 8 and earlier; 7 and earlier; 7, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.55% chance of exploitation within 30 days, higher than 76% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Veeam Service Provider Console to 7.0.0.19551 or 8.0.0.19552, whichever matches your release line, or a later version.
- Read the advisory on veeam.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Veeam | Service Provider Console | 8 and earlier; 7 and earlier; 7; 8 | Not stated |
| Veeam | Veeam Service Provider Console | before 7.0.0.19551; 8.0.0.18054 up to, but not including, 8.0.0.19552 | 7.0.0.19551, 8.0.0.19552 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. Scored by CNA (hackerone.com).
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Deserialization of Untrusted Data
The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
How developers prevent this class of flaw
- If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.
- When deserializing data, populate a new object rather than just deserializing. The result is that the data flows through safe input validation and that the functions are safe.
- Explicitly define a final object() to prevent deserialization.
More Deserialization of Untrusted Data vulnerabilities (CWE-502)
Timeline
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other vulnerabilities in Service Provider Console
- 9.5 Critical severity
- 8.2 High severity
- 9.9 Critical severity
- 7.1 High severity
- 8.5 High severity
- 9.9 Critical severity
Recent Deserialization of Untrusted Data vulnerabilities
- 9.8 Critical severity
- 9.8 Critical severity
- 7.8 High severity
- 8.8 High severity
- 9.8 Critical severity
- 7.2 High severity
Spotted an error? Tell us.