Vulnerability · Published Jul 8, 2022 · Assigned by mitre
CVE-2022-35411
Critical 9.8
In plain English
A critical-severity security flaw in the rpc-py package (PyPI). There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 46.6% (higher than 99% of all known vulnerabilities). Ready-made attack tooling exists: public proof-of-concept code.
Severity (CVSS NVD)9.8Critical
Exploit odds (30 days)46.6%top 1.2% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack tooling1Public PoC
Official 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.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| PyPI | rpc-py | no fix listed | GHSA-8rq8-f485-7v8x |
| PyPI | rpc-py | no fix listed | PYSEC-2026-526 |
Affected products (as reported)
References
- https://medium.com/%40elias.hohl/remote-code-execution-0-day-in-rpc-py-709c76690c30 x_refsource_MISC
- https://github.com/ehtec/rpcpy-exploit x_refsource_MISC
- https://github.com/abersheeran/rpc.py/commit/491e7a841ed9a754796d6ab047a9fb16e23bf8bd x_refsource_MISC
- http://packetstormsecurity.com/files/167872/rpc.py-0.6.0-Remote-Code-Execution.html x_refsource_MISC