CVE-2017-2292
First published: Fri Jun 30 2017(Updated: )
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.
Credit: security@puppet.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Puppet MCollective | <=2.10.3 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2017-2292?
CVE-2017-2292 is considered a critical vulnerability due to its potential for allowing arbitrary code execution on the server.
How do I fix CVE-2017-2292?
To fix CVE-2017-2292, update MCollective to version 2.10.4 or later, which implements YAML.safe_load on input.
Which versions of MCollective are affected by CVE-2017-2292?
CVE-2017-2292 affects all versions of MCollective prior to 2.10.4.
What type of attack can be executed due to CVE-2017-2292?
CVE-2017-2292 can potentially lead to remote code execution attacks if exploited.
Is there a workaround for CVE-2017-2292?
The only recommended solution for CVE-2017-2292 is to upgrade to an unaffected version, as there is no effective workaround.
- agent/references
- agent/type
- agent/softwarecombine
- agent/severity
- agent/author
- agent/weakness
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/event
- agent/first-publish-date
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/puppet
- canonical/puppet mcollective
- version/puppet mcollective/2.10.3