Skip to content
Fencer Intel
critical 9.8

CVE-2022-35411 in the critical feed json

rpc.py vulnerable to Deserialization of Untrusted Data

published 4y ago modified 4mo ago also GHSA-8rq8-f485-7v8x , PYSEC-2026-526 , EUVD-2022-6297

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
46.6%
EPSS 46.6% chance of exploitation in 30 days, percentile 98%
public exploits
1
Exploit-DB

Summary

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.

Patch / fix

Is CVE-2022-35411 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. Published
  2. First public exploit (EDB-50983)

Exploit prediction

46.65% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-50983 rpc.py 0.6.0 - Remote Code Execution (RCE) remote, 2022-07-29
  • medium.com https://medium.com/%40elias.hohl/remote-code-execution-0-day-in-rpc-py-709c76690c30 referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/ehtec/rpcpy-exploit referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/167872/rpc.py-0.6.0-Remote-Code-Execution.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
OSV 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi rpc-py
>=0.4.2, <=0.6.0
 no fix listed

Classification

Weakness
  • CWE-522 Insufficiently Protected Credentials
  • CWE-502 Deserialization of Untrusted Data

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.