Free Range Routing
Vendor:
First CVE: May 13, 2020 · Active for 6 years
1
Total CVEs
Bottom 1%
1.0
Avg CVEs / Year
Bottom 1%
5.3
Avg CVSS
Higher Avg CVSS than 10% of tracked products
0.0%
KEV Rate
Bottom 1%
Trends Over Time
The number and severity of CVEs published that impact Free Range Routing over time
Volume of CVEsAvg CVSS Base Score
First CVE
May 13, 2020
6 years ago
Most Recent CVE
May 13, 2020
2,264 days ago
CVE Severity & Scoring
Free Range Routing1 CVEs
100%
All CVEs352,708 CVEs
45%
40%
11%
Medium
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-2020-12831MEDIUM An issue was discovered in FRRouting FRR (aka Free Range Routing) through 7.3.1. When using the split-config feature, the init script creates an empty config file with world-readab | May 13, 2020 | 5.3 | 19 | 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 Free Range Routing
Top CWEs
Versions
No cataloged versions.