PYSEC-2026-526
rpc.py vulnerable to Deserialization of Untrusted Data
Details
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.
[Per the maintainer](https://github.com/abersheeran/rpc.py/issues/22), rpc.py is not designed for an API that is open to the outside world, and external requests cannot reach rpc.py in real world use.
A [fix](https://github.com/abersheeran/rpc.py/commit/491e7a841ed9a754796d6ab047a9fb16e23bf8bd) exists on the `master` branch. As a workaround, use the following code to turn off pickle in older versions: ``` del SERIALIZER_NAMES[PickleSerializer.name] del SERIALIZER_TYPES[PickleSerializer.content_type]
Are you affected?
Enter the version of the package you're using.
Affected packages
0.4.2No fixed version published yet for rpc-py (pip). Pin to a known-safe version or switch to an alternative.
References
- https://nvd.nist.gov/vuln/detail/CVE-2022-35411[ADVISORY]
- https://github.com/abersheeran/rpc.py/issues/22[WEB]
- https://github.com/abersheeran/rpc.py/commit/491e7a841ed9a754796d6ab047a9fb16e23bf8bd[WEB]
- https://github.com/abersheeran/rpc.py[PACKAGE]
- https://github.com/ehtec/rpcpy-exploit[WEB]
- https://medium.com/%40elias.hohl/remote-code-execution-0-day-in-rpc-py-709c76690c30[WEB]
- https://medium.com/@elias.hohl/remote-code-execution-0-day-in-rpc-py-709c76690c30[WEB]
- http://packetstormsecurity.com/files/167872/rpc.py-0.6.0-Remote-Code-Execution.html[WEB]
- https://pypi.org/project/rpc-py[PACKAGE]
- https://github.com/advisories/GHSA-8rq8-f485-7v8x[ADVISORY]