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.
References
| Link | Resource |
|---|---|
| https://medium.com/@elias.hohl/remote-code-execution-0-day-in-rpc-py-709c76690c30 | Exploit Third Party Advisory |
| https://github.com/abersheeran/rpc.py/commit/491e7a841ed9a754796d6ab047a9fb16e23bf8bd | Patch Third Party Advisory |
| https://github.com/ehtec/rpcpy-exploit | Third Party Advisory |
| http://packetstormsecurity.com/files/167872/rpc.py-0.6.0-Remote-Code-Execution.html | Exploit Third Party Advisory VDB Entry |
Configurations
Information
Published : 2022-07-08 19:15
Updated : 2023-08-08 14:21
NVD link : CVE-2022-35411
Mitre link : CVE-2022-35411
JSON object : View
Products Affected
rpc.py_project
- rpc.py
CWE
CWE-502
Deserialization of Untrusted Data
