Rpc.Py
Vendor:
First CVE: Jul 8, 2022 · Active for 4 years
1
Total CVEs
Bottom 1%
1.0
Avg CVEs / Year
Bottom 1%
9.8
Avg CVSS
Higher Avg CVSS than 87% of tracked products
0.0%
KEV Rate
Bottom 1%
Trends Over Time
The number and severity of CVEs published that impact Rpc.Py over time
Volume of CVEsAvg CVSS Base Score
First CVE
Jul 8, 2022
4 years ago
Most Recent CVE
Jul 8, 2022
1,477 days ago
CVE Severity & Scoring
Rpc.Py1 CVEs
100%
All CVEs352,294 CVEs
45%
40%
11%
Critical
Attack Vector
Local0 (0.0%)
Network1 (100.0%)
Unknown0 (0.0%)
Physical0 (0.0%)
Adjacent Network0 (0.0%)
Attack Complexity
Low1 (100.0%)
High0 (0.0%)
Unknown0 (0.0%)
User Interaction
None1 (100.0%)
Unknown0 (0.0%)
Required0 (0.0%)
Privileges Required
Low0 (0.0%)
High0 (0.0%)
None1 (100.0%)
Unknown0 (0.0%)
Top CVEs
Signals from CVEs in this product scope (1 CVEs).
1 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2022-35411CRITICAL 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 de | Jul 8, 2022 | 9.8 | 65 | NO | YES |
Exploit Exposure
Signals from CVEs in this product scope (1 CVEs).
CISA KEV
0 CVEs
0.0% of CVEs· Bottom 1%
Metasploit
0 CVEs
0.0% of CVEs· Bottom 1%
Nuclei
0 CVEs
0.0% of CVEs· Bottom 1%
ExploitDB
1 CVE
100.0% of CVEs· 93rd percentile
Social Chatter
Signals from CVEs in this product scope (1 CVEs).
Media Mentions
Signals from CVEs in this product scope (1 CVEs).
Top CNAs Publishing CVEs For Rpc.Py
Top CWEs
Versions
No cataloged versions.