CVE-2022-31605
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedNVFLARE, 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe vulnerability exists in NVFLARE's utils module where YAML files are loaded using yaml.load() instead of yaml.safe_load(). The unsafe yaml.load() function allows deserialization of arbitrary Python objects, enabling attackers to craft malicious YAML payloads that can execute arbitrary code on the target system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.1.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if NVFLARE is installedRun 'pip show nvflare' or 'pip list | grep -i nvflare' to find installed packagesAffected if NVFLARE is installed and version is below 2.1.2
-
Find the utils module locationRun 'python -c "import nvflare.utils; print(nvflare.utils.__file__)"' to locate the utils module file pathAffected if The utils module file path is found in an NVFLARE installation below version 2.1.2
-
Search for unsafe yaml.load() callsSearch the utils module directory for 'yaml.load(' using grep: 'grep -r "yaml.load" <path_to_utils>' or 'grep -rn "yaml.load" .' within the utils directoryAffected if Code contains yaml.load() instead of yaml.safe_load()
-
Identify YAML processing entry pointsReview the utils module for functions that accept and process YAML configuration files or user-supplied YAML dataAffected if The utils module processes YAML files and contains the unsafe yaml.load() call
You are affected if NVFLARE version is below 2.1.1 and the codebase contains yaml.load() calls in the utils module that process external YAML files.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.1.2
Replace all instances of yaml.load() with yaml.safe_load() in the utils module and upgrade to NVFLARE version 2.1.2 or later to remediate this vulnerability.
NVFLARE 2.1.2 or later
- Check the current installed version of NVFLARE (e.g., running 'pip show nvflare' or checking the package version in your environment)
- Upgrade NVFLARE to version 2.1.2 or later using the appropriate package manager (e.g., 'pip install --upgrade nvflare' or 'pip install nvflare>=2.1.2')
- Verify the upgrade was successful by checking the installed version matches or exceeds 2.1.2
- Test that your NVFLARE deployment functions normally after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31605 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-31605 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data