pytorch-lightning is vulnerable to Deserialization of Untrusted Data
CVE-2021-4118 · GHSA-2vj5-px25-gjrp · published 2022-01-06 · updated 2024-10-25
- Severity
- High
- CVSS score
- 7.8
- Chance of exploitation (EPSS)
- 1.0%
- Fixed in
- 1.6.0
pytorch-lightning is vulnerable to Deserialization of Untrusted Data.
Upgrade pytorch-lightning to 1.6.0 or later.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| pytorch-lightning | PyPI | < 1.6.0 | 1.6.0 |
- CriticalLMDeploy has Remote Code Execution by Pickle Deserialization via handle_zmq_recv in lmdeploy/lmdeploy/pytorch/disagg/conn/engine_conn.pylmdeploy
- CriticalLMdeploy has Remote Code Execution by Pickle Deserialization via zmq_rpc.call_and_response() in InterLM/lmdeploylmdeploy
- CriticalSGLang: Unauthenticated RCE via --enable-custom-logit-processorsglang
- CriticalSGLanG: Multimodal scheduler deserializes untrusted pickle data on 0.0.0.0 ROUTER socketsglang
- Criticaln8n: HTTP Request Node Pagination Prototype Pollution to RCEn8n, n8n, n8n
- Criticaln8n Has an XML Node Prototype Pollution Patch Bypassn8n, n8n, n8n
- CriticalCompromise of PyTorch Lightning PyPi Package Versionspytorch-lightning, pytorch-lightning
- CriticalPyTorch Lightning path traversal vulnerabilitylightning, pytorch-lightning
- Criticalpytorch-lightning vulnerable to Arbitrary File Write via /v1/runs API endpointlightning, pytorch-lightning
- CriticalRemote code execution in pytorch lightninglightning, pytorch-lightning
- CriticalCode Injection in PyTorch Lightningpytorch-lightning
- HighPyTorch Lightning load_from_checkpoint has an insecure checkpoint deserializationpytorch-lightning
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.