Rply
Vendor:
First CVE: Jan 28, 2014 · Active for 12 years
1
Total CVEs
Bottom 1%
1.0
Avg CVEs / Year
Bottom 1%
2.1
Avg CVSS
Bottom 1%
0.0%
KEV Rate
Bottom 1%
Trends Over Time
The number and severity of CVEs published that impact Rply over time
Volume of CVEsAvg CVSS Base Score
First CVE
Jan 28, 2014
12 years ago
Most Recent CVE
Jan 28, 2014
4,563 days ago
CVE Severity & Scoring
Rply1 CVEs
100%
All CVEs352,785 CVEs
45%
40%
11%
Low
Attack Vector
Local0 (0.0%)
Network0 (0.0%)
Unknown1 (100.0%)
Physical0 (0.0%)
Adjacent Network0 (0.0%)
Attack Complexity
Low0 (0.0%)
High0 (0.0%)
Unknown1 (100.0%)
User Interaction
None0 (0.0%)
Unknown1 (100.0%)
Required0 (0.0%)
Privileges Required
Low0 (0.0%)
High0 (0.0%)
None0 (0.0%)
Unknown1 (100.0%)
Top CVEs
Signals from CVEs in this product scope (1 CVEs).
1 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
The parser cache functionality in parsergenerator.py in RPLY (aka python-rply) before 0.7.1 allows local users to spoof cache data by pre-creating a temporary rply-*.json file with | Jan 28, 2014 | 2.1 | 11 | NO | NO |
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
0 CVEs
0.0% of CVEs· Bottom 1%
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 Rply
Versions
No cataloged versions.