CVE-2022-35411 rpc.py vulnerable to Deserialization of Untrusted Data
Unauthenticated attackers can achieve remote code execution by sending a specific HTTP header to trigger unsafe pickle deserialization in the rpc.py library.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2022-35411?
CVE-2022-35411 is a critical unsafe deserialization vulnerability in n/a, published on 8 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
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.
Weakness: CWE-522
Which versions are affected by CVE-2022-35411?
3 open source packages ship an affected version, including rpc-py and rpc.py. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
rpc-py PyPI | From 0.4.2 to 0.6.0 | None |
rpc-py PyPI | From 0.4.2 to 0.6.0 | None |
rpc.py PyPI | From 0.4.2 to 0.6.0 | None |
Products include Rpc.py Project Rpc.py.
How do I fix CVE-2022-35411?
No fix has been published for CVE-2022-35411 yet. Limit exposure of the affected software until one is available.
Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.
Is CVE-2022-35411 being exploited?
There is no known exploitation of CVE-2022-35411 in the wild and no public exploit code.
Public exploit code: 1 Exploit-DB entry and 2 proofs of concept on GitHub.
Sources
Also known as GHSA-8rq8-f485-7v8x, PYSEC-2026-526.