Skip to content

Unsafe yaml deserialization in NVFlare

Critical severity GitHub Reviewed Published Jun 21, 2022 in NVIDIA/NVFlare • Updated Sep 2, 2023

Package

pip nvflare (pip)

Affected versions

< 2.1.2

Patched versions

2.1.2

Description

Impact

NVFLARE 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.

All versions before 2.1.2 are affected.
CVSS Score = 9.8
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Patches

The patch will be included in nvflare==2.1.2

Workarounds

Change yaml.load() to yaml.safe_load()

Additional information

Issue Found by: Oliver Sellwood (@Nintorac)

References

@chesterxgchen chesterxgchen published to NVIDIA/NVFlare Jun 21, 2022
Published to the GitHub Advisory Database Jun 22, 2022
Reviewed Jun 22, 2022
Published by the National Vulnerability Database Jul 1, 2022
Last updated Sep 2, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.308%
(70th percentile)

Weaknesses

CVE ID

CVE-2022-31605

GHSA ID

GHSA-hrf3-622q-8366

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.