CVE-2022-31604Critical· 9.8▾ MidnightUnsafe deserialisation in the PKI implementation scheme of NVFlare
▾ Midnight zone — Critical, or high with PoC / in-the-wild
impact 53.9 · likelihood 0.4 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
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
1.9%
1.9% → 2.1%
NVFLARE contains a vulnerability in its PKI implementation module, where The CA credentials are transported via pickle and no safe deserialization. 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
The patch will be included in nvflare==2.1.2
Replace pickle serialization with JSON and change the code accordingly
Additional information Issue Found by: Oliver Sellwood (@Nintorac)
nvflare < 2.1.2Upgrade to a patched release:
nvflare 2.1.2Connected by shared product, vendor, weakness, or advisory.
CVE-2022-21822High· 7.5Allocation of Resources Without Limits or Throttling in nvflare
CVE-2022-31605Critical· 9.8Unsafe yaml deserialization in NVFlare
CVE-2022-34668Critical· 9.8NVFLARE unsafe deserialization due to Pickle