Vulnerability in Rpc.py Project
CVE-2022-35411
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.
EPSS: 0.461 (98.7th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 9.8 (Critical). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
Affected products
- Rpc.py_project Rpc.py
- N/a — versions n/a
Weakness classification (CWE)
Public proof-of-concept exploits
References
- cve@mitre.org (Exploit, x_refsource_MISC)
- cve@mitre.org (Exploit, Third Party Advisory, x_refsource_MISC)
- cve@mitre.org (Patch, Third Party Advisory, x_refsource_MISC)
- cve@mitre.org (Exploit, VDB Entry, Third Party Advisory, x_refsource_MISC)
Frequently asked questions
- What is CVE-2022-35411?
- CVE-2022-35411 is a critical-severity vulnerability in Rpc.py Project, classified under Insufficiently Protected Credentials. CVSS score: 9.8/10. Published 2022-07-08.
- How severe is CVE-2022-35411?
- Critical severity. CVSS v3 base score is 9.8 out of 10.
- Is CVE-2022-35411 known to be exploited?
- 11 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.