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.
Vendor
rpc.py project vulnerabilities
1 published CVE affecting rpc.py project, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 1
- Critical
- 1
- High
- 0
- Medium
- 0
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Products
Latest rpc.py project CVEs
Newest publication first
-
CriticalCVSS 9.8 EPSS 46.6% Public exploit PoC
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.