CVE-2022-31605: PYSEC-2022-232 - 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.

CVE-2022-31605 · Severity: low · CVSS 3.1 · Published 2022-07-01

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.

Technologies: nvflare (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2022-31605 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2022-31605 being exploited in the wild.
How severe is CVE-2022-31605?
Low severity, with a CVSS score of 3.1, published 1 July 2022.
Which products and versions are affected?
nvflare (PyPI) ECOSYSTEM:introduced=0,fixed=2.1.2.
Is there a fix for CVE-2022-31605?
Yes. nvflare (PyPI): upgrade to 2.1.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2022-31605?
Check whether you run nvflare (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • nvflare (PyPI): upgrade to 2.1.2 or later
    pip install "nvflare>=2.1.2"

Affected products

  • nvflare (PyPI) ECOSYSTEM:introduced=0,fixed=2.1.2

Identifiers

  • CVE-2022-31605
  • GHSA-hrf3-622q-8366
  • PYSEC-2022-232

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.