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.
The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.
Link | Tags |
---|---|
https://medium.com/%40elias.hohl/remote-code-execution-0-day-in-rpc-py-709c76690c30 | exploit |
https://github.com/ehtec/rpcpy-exploit | third party advisory exploit |
https://github.com/abersheeran/rpc.py/commit/491e7a841ed9a754796d6ab047a9fb16e23bf8bd | third party advisory patch |
http://packetstormsecurity.com/files/167872/rpc.py-0.6.0-Remote-Code-Execution.html | exploit vdb entry third party advisory |