CVE-2017-2292 json
Versions of MCollective prior to 2.10.4 deserialized YAML from agents without calling safe_load, allowing the potential for arbitrary code…
published 2017-06-30 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-11475
- cvss
- 9.0
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.2%
- EPSS 2.2% chance of exploitation in 30 days, percentile 82%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- mcollective Debian 12 2.12.0+dfsg-1
debian advisories DEBIAN-CVE-2017-2292
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2017-2292 updated cvss 8.1
mcollective: RCE via YAML deserialization
-
Red Hat OpenShift Enterprise 2 ruby193-mcollectiveaffected: no fix planned “Will not fix”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
2.18% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.0 | CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Affected products
- Puppet mcollective, Puppet, Puppet Enterprise
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
References
-
security.gentoo.org
/glsa/201709-01
vendor-advisory
-
puppet.com
/security/cve/cve-2017-2292
vendor-advisory
Sources
- CVE List CVE-2017-2292
- NVD CVE-2017-2292
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.