VMware vCenter Server: Deserialization of Untrusted Data
CVE-2022-31680 is a critical-severity deserialization of untrusted data vulnerability in VMware vCenter Server, with a CVSS 3.1 base score of 9.1 out of 10. It can be exploited remotely over the network by an attacker with administrator privileges, without any action from a user. Affected VMware vCenter Server versions: VMware vCenter Server 6.5 prior to U3u. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 31.1% chance of exploitation within 30 days, which is in the top 1.71% of all scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Vcenter Server to 6.5 or a later version.
- Read the advisory on vmware.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| VMware vCenter Server | VMware vCenter Server | VMware vCenter Server 6.5 prior to U3u | Not stated |
| VMware | Vcenter Server | before 6.5; 6.5 | 6.5 |
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
- HighAdministrator-level access is required first.
- 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.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H. Scored by NVD.
Official description
The vCenter Server contains an unsafe deserialisation vulnerability in the PSC (Platform services controller). A malicious actor with admin access on vCenter server may exploit this issue to execute arbitrary code on the underlying operating system that hosts the vCenter Server.
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
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Technical write-ups (may include proof of concept)
- talosintelligence.com/vulnerability_reports/TALOS-2022-1587Exploit, Third Party Advisory
Other vulnerabilities in VMware vCenter Server
- 9.8 Critical severity
- 9.8 Critical severity
- 7.8 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 7.2 High severity
Recent Deserialization of Untrusted Data vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 8.0 High severity
- 7.5 High severity
- 7.5 High severity
- 8.0 High severity
Spotted an error? Tell us.