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 |
---|---|
http://packetstormsecurity.com/files/167872/rpc.py-0.6.0-Remote-Code-Execution.html | Exploit Third Party Advisory VDB Entry |
https://github.com/abersheeran/rpc.py/commit/491e7a841ed9a754796d6ab047a9fb16e23bf8bd | Patch Third Party Advisory |
https://github.com/ehtec/rpcpy-exploit | Exploit Third Party Advisory |
https://medium.com/%40elias.hohl/remote-code-execution-0-day-in-rpc-py-709c76690c30 | Exploit |
Configurations
History
No history.
Information
Published : 2022-07-08 19:15
Updated : 2024-02-09 03:16
NVD link : CVE-2022-35411
Mitre link : CVE-2022-35411
CVE.ORG link : CVE-2022-35411
JSON object : View
Products Affected
rpc.py_project
- rpc.py
CWE
CWE-522
Insufficiently Protected Credentials