GitHub Advisoryadvisory · PyPI
GHSA-8rq8-f485-7v8x rpc.py vulnerable to Deserialization of Untrusted Data
CRITICAL
Official page ↗
- Aliases
- CVE-2022-35411
- Ecosystem
- PyPI
- Packages
- rpc.py
- Severity
- Critical
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Weaknesses
- CWE-502, CWE-522
- Reviewed
- 2022-07-12
Affected packages
• PyPI rpc.py: >= 0.4.2, <= 0.6.0 (no fix yet)
Description
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, 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 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]
Related
Alias · CVE (1)
- CVE-2022-35411 rpc.py through 0.6.0 allows Remote Code Execution because an unpickle occurs when the "serializer: pickle" HTTP header is sent. vulnerability
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