CVE-2022-35411
highPriorität · beachten · 65EPSS 0.457 · 99. PerzentilExploit · PoCEUUSEPSS · bewertet 2026-10-24
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.
cvss
Technischer Schweregrad, 0–10. Eine Zeile je Quelle.
Basiswert 0–10 · höher = schwerwiegender · Vektor überfahren zum Auflösen⚠ Quellen uneinig · high–critical · 7.5–9.8
schwächen
Die CWE-Schwächeklassen, zu denen dies gehört.
Exploits (3)
Öffentlicher Proof-of-Concept- und Exploit-Code.
- EDB-50983rpc.py 0.6.0 - Remote Code Execution (RCE)PoC · exploit_db
- Neo-okami/CVE-2022-35411rpc.py 0.6.0 - Remote Code Execution (RCE)PoC · poc_in_github
betroffene Produkte (3)
Betroffene Produkte und Versionsbereiche.
Advisories (2)
Hersteller- und Ökosystem-Meldungen dazu.
- GHSA-8rq8-f485-7v8xrpc.py vulnerable to Deserialization of Untrusted Data2022-07-09ghsa · osvUS
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. [Per the maintainer](https://github.com/abersheeran/rpc.py/issues/22), rpc.py is not designed for an API that is open to the outside world, and external requests cannot reach rpc.py in real world use. A [fix](https://github.com/abersheeran/rpc.py/commit/491e7a841ed9a754796d6ab047a9fb16e23bf8bd) exists on the `master` branch. As a workaround, use the following code to turn off pickle in older versions: ``` del SERIALIZER_NAMES[PickleSerializer.name] del SERIALIZER_TYPES[PickleSerializer.content_type]
- PYSEC-2026-526rpc.py vulnerable to Deserialization of Untrusted Data2026-06-29vendor · osvUS
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. [Per the maintainer](https://github.com/abersheeran/rpc.py/issues/22), rpc.py is not designed for an API that is open to the outside world, and external requests cannot reach rpc.py in real world use. A [fix](https://github.com/abersheeran/rpc.py/commit/491e7a841ed9a754796d6ab047a9fb16e23bf8bd) exists on the `master` branch. As a workaround, use the following code to turn off pickle in older versions: ``` del SERIALIZER_NAMES[PickleSerializer.name] del SERIALIZER_TYPES[PickleSerializer.content_type]
auch bekannt als (6)
Weitere Namen und Kennungen dieser Entität.
quellen
Welche Quellen diesen Datensatz belegen und wann.
Referenzen (15)
Externe Belege — Patches, Meldungen, Analysen.
- https://cxsecurity.com/cveshow/CVE-2022-35411/cnnvd
- https://cxsecurity.com/issue/WLB-2022080022cnnvd
- https://github.com/abersheeran/rpc.py/commit/491e7a841ed9a754796d6ab047a9fb16e23bf8bdcnnvd
- https://github.com/ehtec/rpcpy-exploitcnnvd
- https://medium.com/@elias.hohl/remote-code-execution-0-day-in-rpc-py-709c76690c30cnnvd
- https://packetstormsecurity.com/files/167872/rpc.py-0.6.0-Remote-Code-Execution.htmlcnnvd
- https://www.exploit-db.com/exploits/50983cnnvd
- http://packetstormsecurity.com/files/167872/rpc.py-0.6.0-Remote-Code-Execution.htmlenisa_euvd
Angreifer nutzen Schwachstellen wie diese gegen im Internet exponierte Dienste aus. Sehen Sie mit einem kostenlosen Passiv-Scan, was exponiert ist.
Kostenloser Scan