Skip to content
Connect AISign inSign up free
CVE-2017-2292Not scoredCWE-502

CVE-2017-2292: Puppet mcollective, Puppet, Puppet Enterprise vulnerability

Puppet · mcollective, Puppet, Puppet Enterprise

Vendor fix available · Affected: Puppet mcollective, Puppet, Puppet Enterprise · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

2.2%probability of exploitation in the next 30 days
82nd percentile
050100

Higher than 82% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

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 is to call YAML.safe_load on input. This has been tested in all Puppet-supplied MCollective plugins, but there is a chance that third-party plugins could rely on this insecure behavior.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • Puppet · mcollective, Puppet, Puppet EnterprisePuppet Enterprise prior to 2016.4.5, Puppet Enterprise 2016…

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV
Not listed
Public check
No public nuclei template
Vendor
Puppet
Published
June 2017

CoverageNo articles yet

No CyberSIXT article names CVE-2017-2292 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References