← Back
CVE-2022-35411
Unsafe Deserialization in rpc-py (CVE-2022-35411)
Summary
vulnerability in rpc-py (CVE-2022-35411). Successful exploitation can lead to full system takeover. Exploitable via ``master``.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2022-35411** has been found in rpc-py.
Attackers can target a specific entry point like ``master`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "rpc-py CVE-2022-35411" on the vendor's site.
CVE-2022-35411 (rpc-py) — CWE-502 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `master`
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**unsafe deserialization** (CWE-502) exists in rpc-py. Attackers reach the vulnerable code path via ``master`` without authentication.
📍 Affected scope
rpc-py — . Attack surface: `master`.
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'rpc-py' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'rpc-py' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `rpc-py` を grep し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
rpc-py
[{"type":"ECOSYSTEM","events":[{"introduced":"0.4.2"},{"last_affected":"0.6.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2022-35411
- advisory https://github.com/advisories/GHSA-8rq8-f485-7v8x
- package https://github.com/abersheeran/rpc.py
- package https://pypi.org/project/rpc-py
- web https://github.com/abersheeran/rpc.py/issues/22
- web https://github.com/abersheeran/rpc.py/commit/491e7a841ed9a754796d6ab047a9fb16e23bf8bd
- web https://github.com/ehtec/rpcpy-exploit
- web https://medium.com/%40elias.hohl/remote-code-execution-0-day-in-rpc-py-709c76690c30
- web https://medium.com/@elias.hohl/remote-code-execution-0-day-in-rpc-py-709c76690c30
- web http://packetstormsecurity.com/files/167872/rpc.py-0.6.0-Remote-Code-Execution.html