Skip to content

Allocation of Resources Without Limits or Throttling in nvflare

High severity GitHub Reviewed Published Mar 17, 2022 in NVIDIA/NVFlare • Updated Jan 27, 2023

Package

pip nvflare (pip)

Affected versions

< 2.0.16

Patched versions

2.0.16

Description

Impact

NVIDIA FLARE contains a vulnerability in Admin Interface, where an un-authorized attacker can cause Allocation of Resources Without Limits or Throttling, which may lead to cause system unavailable

All versions before 2.0.16 are affected.

Patches

The patch will be included in nvflare==2.0.16.

Workarounds

The changes in commits NVIDIA/NVFlare@93588b3 and NVIDIA/NVFlare@93588b3 can be applied to any version of the NVIDIA FLARE without any adverse effect.

Additional information

Issue Found on: 2022.3.3
Issue Found by: Oliver Sellwood (@Nintorac)

References

@IsaacYangSLA IsaacYangSLA published to NVIDIA/NVFlare Mar 17, 2022
Published by the National Vulnerability Database Mar 17, 2022
Published to the GitHub Advisory Database Mar 18, 2022
Reviewed Mar 18, 2022
Last updated Jan 27, 2023

Severity

High

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
None
Integrity
None
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:N/I:N/A:H

EPSS score

0.044%
(14th percentile)

Weaknesses

CVE ID

CVE-2022-21822

GHSA ID

GHSA-jx8f-cpx7-fv47

Source code

Credits

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