CVE-2017-2292

Description

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.

Category

9.0
CVSS
Severity: Critical
CVSS 3.0 •
CVSS 2.0 •
EPSS 1.93% Top 20%
Vendor Advisory gentoo.org Vendor Advisory puppet.com
Affected: Puppet mcollective, Puppet, Puppet Enterprise
Published at:
Updated at:

References

Link Tags
https://puppet.com/security/cve/cve-2017-2292 vendor advisory
https://security.gentoo.org/glsa/201709-01 vendor advisory

Frequently Asked Questions

What is the severity of CVE-2017-2292?
CVE-2017-2292 has been scored as a critical severity vulnerability.
How to fix CVE-2017-2292?
To fix CVE-2017-2292, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2017-2292 being actively exploited in the wild?
It is possible that CVE-2017-2292 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~2% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2017-2292?
CVE-2017-2292 affects Puppet mcollective, Puppet, Puppet Enterprise.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.