CVE-2022-35411
rpc.py vulnerable to Deserialization of Untrusted Data
Public exploit code
Working exploit or proof of concept code has been published for this vulnerability. Treat unpatched systems as at risk.
- rpc.py 0.6.0 - Remote Code Execution (RCE)2022-07-29 · remote · python
Impact
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]
Affected packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| pip | rpc.py | >= 0.4.2, <= 0.6.0 | none recorded |
Affected products
| Vendor | Product | Affected versions |
|---|---|---|
| Rpc.Py Project | Rpc.Py | from 0.4.2 through 0.6.0 |
Weakness classification
References
- NVD record
- CVE.org record
- GitHub advisory
- http://packetstormsecurity.com/files/167872/rpc.py-0.6.0-Remote-Code-Execution.html
- https://github.com/abersheeran/rpc.py/commit/491e7a841ed9a754796d6ab047a9fb16e23bf8bd
- https://github.com/ehtec/rpcpy-exploit
- https://medium.com/%40elias.hohl/remote-code-execution-0-day-in-rpc-py-709c76690c30
- https://github.com/advisories/GHSA-8rq8-f485-7v8x
- https://nvd.nist.gov/vuln/detail/CVE-2022-35411
- https://medium.com/@elias.hohl/remote-code-execution-0-day-in-rpc-py-709c76690c30
- https://github.com/abersheeran/rpc.py/issues/22