CVE-2022-35411Published Jul 8, 2022 · Jul 8Updated Oct 28
rpc.py vulnerable to Deserialization of Untrusted Data
Critical9.8Fix available
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| rpc-py PyPI |
| No fix yet |
Original description
rpc.py through 0.6.0 allows Remote Code Execution because an unpickle occurs when the "serializer: pickle" HTTP header is sent. In other words, although JSON (not Pickle) is the default data format, an unauthenticated client can cause the data to be processed with unpickle.
From the CVE record · mitre
References
- medium.com/%40elias.hohl/remote-code-execution-0-day-in-rpc-py-709c76690c30Exploit
- github.com/ehtec/rpcpy-exploitExploit
- github.com/abersheeran/rpc.py/commit/491e7a841ed9a754796d6ab047a9fb16e23bf8bdPatch
- packetstormsecurity.com/files/167872/rpc.py-0.6.0-Remote-Code-Execution.htmlExploit
- github.com/CVEProject/cvelistV5/tree/main/cves/2022/35xxx/CVE-2022-35411.json
- nvd.nist.gov/vuln/detail/CVE-2022-35411
- github.com/abersheeran/rpc.py/issues/22
- github.com/abersheeran/rpc.py
- medium.com/@elias.hohl/remote-code-execution-0-day-in-rpc-py-709c76690c30
- pypi.org/project/rpc-py
- github.com/advisories/GHSA-8rq8-f485-7v8x