CVE-2022-35411
Rpc.py Project Rpc.py vulnerability
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.
High priority: this vulnerability is rated critical and can be attacked over the network without a login.
Affected products
Rpc.py. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Rpc.py Project Rpc.py runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/abersheeran/rpc.py/commit/491e7a841ed9a754796d6ab047a9fb16e23bf8bd · Patch
- packetstormsecurity.com/files/167872/rpc.py-0.6.0-Remote-Code-Execution.html · Exploit
- github.com/ehtec/rpcpy-exploit · Exploit
- medium.com/%40elias.hohl/remote-code-execution-0-day-in-rpc-py-709c76690c30 · Exploit
- nvd.nist.gov/vuln/detail/CVE-2022-35411
- medium.com/@elias.hohl/remote-code-execution-0-day-in-rpc-py-709c76690c30
- github.com/abersheeran/rpc.py/issues/22
- github.com/advisories/GHSA-8rq8-f485-7v8x
- nvd.nist.gov/vuln/detail/CVE-2022-35411
- cve.org/CVERecord?id=CVE-2022-35411
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.