Mcollective
Vendor:
First CVE: Aug 12, 2014 · Active for 11 years
2
Total CVEs
Bottom 1%
1.0
Avg CVEs / Year
Bottom 1%
6.7
Avg CVSS
Higher Avg CVSS than 83% of tracked products
0.0%
KEV Rate
Bottom 1%
Trends Over Time
The number and severity of CVEs published that impact Mcollective over time
Volume of CVEsAvg CVSS Base Score
First CVE
Aug 12, 2014
11 years ago
Most Recent CVE
Jun 30, 2017
3,314 days ago
CVE Severity & Scoring
Mcollective2 CVEs
50%
50%
All CVEs352,785 CVEs
45%
40%
11%
MediumCritical
Attack Vector
Local0 (0.0%)
Network1 (50.0%)
Unknown1 (50.0%)
Physical0 (0.0%)
Adjacent Network0 (0.0%)
Attack Complexity
Low1 (50.0%)
High0 (0.0%)
Unknown1 (50.0%)
User Interaction
None1 (50.0%)
Unknown1 (50.0%)
Required0 (0.0%)
Privileges Required
Low0 (0.0%)
High1 (50.0%)
None0 (0.0%)
Unknown1 (50.0%)
Top CVEs
Signals from CVEs in this product scope (2 CVEs).
2 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2017-2292CRITICAL Versions of MCollective prior to 2.10.4 deserialized YAML from agents without calling safe_load, allowing the potential for arbitrary code execution on the server. The fix for this | Jun 30, 2017 | 9.0 | 30 | NO | NO |
CVE-2014-3251MEDIUM The MCollective aes_security plugin, as used in Puppet Enterprise before 3.3.0 and Mcollective before 2.5.3, does not properly validate new server certificates based on the CA cert | Aug 12, 2014 | 4.4 | 17 | NO | NO |
Exploit Exposure
Signals from CVEs in this product scope (2 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 (2 CVEs).
Media Mentions
Signals from CVEs in this product scope (2 CVEs).
Top CNAs Publishing CVEs For Mcollective
Top CWEs
Versions
No cataloged versions.