CVE-2022-35411

EPSS 45.9%

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.

Affected products

n/a · n/a

public PoCs found — 4

githubgithub.com/CSpanias/rpc-rce.py★ 2 githubgithub.com/Neo-okami/CVE-2022-35411★ 0 cve_referencepacketstormsecurity.com/files/167872/rpc.py-0.6.0-Remote-Code-Execution.htmlunverified exploitdbwww.exploit-db.com/exploits/50983unverified

⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.

Want to know if your infrastructure is exposed to this?

Talk to TrueHacking →

References

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