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.

Published · last modified .

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.

EPSS exploit prediction

EPSS: 0.457 (98.8th percentile), scored .

Moderate probability of exploitation in the next 30 days — watch for active exploitation reports. 99th percentile — 98.8% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2022-35411: held from 0.461 to 0.457.

EPSS over last 30 days · oldest: 0.461 · newest: 0.457 · change: -0.004

Affected products

Weakness classification (CWE)

Public proof-of-concept exploits

References

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.