CVE-2022-34668Critical· 9.8▾ AbyssalPoC availableNVFLARE unsafe deserialization due to Pickle
▾ Abyssal zone — Critical with a public exploit or in-the-wild use
impact 53.9 · likelihood 2.2 · exploitation 12
A public proof-of-concept already exists for this vulnerability — see Exploit availability below.
Public exploit / PoC code seen in 1 source. Availability, not in-the-wild use.
Exploit-prediction probability, daily snapshots since Jul 8.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
8.5%
8.5% → 11%
Exploit-DB (last check)
NVFLARE contains a vulnerability where deserialization of Untrusted Data due to Pickle usage 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.4 are affected.
CVSS Score = 9.8
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
The patch is included in nvflare==2.1.4 This new version uses MessagePack instead of Pickle to do serialization and deserialization.
Some object serializations supported by Pickle are not supported by MessagePack. We have provided out of box support for some built-in NVFLARE objects. For object serializations unsupported by MessagePack, the user will need to convert the objects to numpy or bytes before sending over to remote machines. The list of supported object types are listed in https://github.com/NVIDIA/NVFlare/blob/2.1/nvflare/fuel/utils/fobs/README.rst
No workarounds available.
Issue Found by: Oliver Sellwood (Nintorac) and Elias Hohl
nvflare < 2.1.4Upgrade to a patched release:
nvflare 2.1.4Connected by shared product, vendor, weakness, or advisory.
CVE-2022-31604Critical· 9.8Unsafe deserialisation in the PKI implementation scheme of NVFlare
CVE-2022-21822High· 7.5Allocation of Resources Without Limits or Throttling in nvflare
CVE-2022-31605Critical· 9.8Unsafe yaml deserialization in NVFlare