NVIDIA FLARE: Deserialization of Untrusted Data
CVE-2022-31605 is a high-severity deserialization of untrusted data vulnerability in NVIDIA FLARE from NVIDIA, with a CVSS 2.0 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected NVIDIA FLARE versions: All versions prior to 2.1.2. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 2.13% chance of exploitation within 30 days, higher than 82% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Nvflare to 2.1.2 or a later version.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| NVIDIA | NVIDIA FLARE | All versions prior to 2.1.2 | Not stated |
| NVIDIA | Nvflare | before 2.1.2 | 2.1.2 |
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
- Access vector
- NetworkCan be exploited remotely over a network.
- Access complexity
- LowNo special conditions are needed.
- Authentication
- NoneNo login is needed.
- Confidentiality
- PartialSome data can be read.
- Integrity
- PartialSome data can be modified.
- Availability
- PartialAvailability is reduced.
Vector: AV:N/AC:L/Au:N/C:P/I:P/A:P. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 9.8 | Critical | CNA (nvidia.com) |
| CVSS 2.0 | 7.5 | High | NVD |
Official description
NVFLARE, versions prior to 2.1.2, contains a vulnerability in its utils module, where YAML files are loaded via yaml.load() instead of yaml.safe_load(). The deserialization of Untrusted Data, may allow an unprivileged network attacker to cause Remote Code Execution, Denial Of Service, and Impact to both Confidentiality and Integrity.
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
Advisories
- github.com/NVIDIA/NVFlare/security/advisories/GHSA-hrf3-622q-8366Third Party Advisory
Other vulnerabilities in NVIDIA FLARE
- 8.6 High severity
- 9.8 Critical severity
- 7.5 High severity
- 7.8 High severity
Recent Deserialization of Untrusted Data vulnerabilities
- 8.8 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.