PatchTheCVEmcollective vulnerabilities and fixes
Recent CVEs affecting mcollective, with upgrade or downgrade steps. 2 tracked.
mcollective has 2 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 2. Most recent: 2017-06-30. Highest priority: CVE-2017-2292 (score 52/100).
- CVE-2017-2292 CRITICAL 9.0 UPGRADE Versions of MCollective prior to 2.10.4 deserialized YAML from agents without calling safe_load, allowing the
- CVE-2014-3251 MEDIUM 4.4 UPGRADE MITIGATE The MCollective aes_security plugin, as used in Puppet Enterprise before 3.3.0 and Mcollective before 2.5.3, d
FAQ
How do I fix mcollective vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is mcollective being exploited right now?
None of the tracked mcollective CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which mcollective CVE should I patch first?
CVE-2017-2292 currently ranks highest (52/100): Versions of MCollective prior to 2.10.4 deserialized YAML from agents without calling safe_load, allowing the .