Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%
Get alerts for future matching vulnerabilitiesLog in to subscribe
I. Basic Information for CVE-2022-35411
Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
N/A
Source: NVD (National Vulnerability Database)
Vulnerability 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.
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
rpc.py 代码问题漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
rpc.py是中国Aber个人开发者的一个快速而强大的基于 ASGI/WSGI 的 RPC 框架。 rpc.py 0.6.0版本及之前版本存在安全漏洞。攻击者利用该漏洞使用 unpickle 处理数据。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)
Affected Products
VendorProductAffected VersionsCPESubscribe
-n/a n/a -
II. Public POCs for CVE-2022-35411
#POC DescriptionSource LinkShenlong Link
1Nonehttps://github.com/fuzzlove/CVE-2022-35411POC Details
2Exploit for CVE-2022-35411 — Unauthenticated RCE in rpc.py (<= 0.6.0)https://github.com/CSpanias/rpc-rce.pyPOC Details
AI-Generated POCPremium

No public POC found.

Login to generate AI POC
III. Intelligence Information for CVE-2022-35411
Please Login to view more intelligence information
IV. Related Vulnerabilities
V. Comments for CVE-2022-35411

No comments yet


Leave a comment