Read the docs
TI-2017-01573 Aliases CVE-2017-2292GHSA-9hgj-f7f3-cph7

Deserialization of untrusted data in Puppet mcollective, Puppet, Puppet Enterprise

Priority MEDIUM 43CWE-502Published · Updated

Key facts

Attack vector
Network
Privileges required
High
User interaction
None
Attack complexity
Low
Impact type
Code execution
Confidentiality · integrity · availability
High · High · Low
Fix status
Will not fix Red Hat: no fix planned

Attack profile from CVSS 3.0 · NVD. Fix status from CNA and Red Hat. Impact type from CWE-502.

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.

Why it matters now

EPSS 0.0218 82nd percentileScored 2026-11-07
Fix Will not fix Red Hat: no fix planned

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
Puppetmcollective, Puppet, Puppet EnterprisePuppet Enterprise prior to 2016.4.5, Puppet Enterprise 2016.5.x, Puppet Enterprise 2017.1.x, Puppet Agent prior to 1.10.1—No fix listedCNA
  • mcollective, Puppet, Puppet Enterprise VendorPuppet Affected Puppet Enterprise prior to 2016.4.5, Puppet Enterprise 2016.5.x, Puppet Enterprise 2017.1.x, Puppet Agent prior to 1.10.1 Fixed in — No fix listed CNA

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:puppet:mcollective:*:*:*:*:*:puppet:*:*up to 2.10.3VulnerablePuppet
  • cpe:2.3:a:puppet:mcollective:*:*:*:*:*:puppet:*:* Versions up to 2.10.3 Vulnerable ·Puppet

Remediation

No fixed version listed by the sources yet.

Vendor assessments

Red Hat

Red Hat rating: Important. Red Hat's page for this CVE →

ProductStatusPlan or fix
Red Hat OpenShift Enterprise 2AffectedNo fix planned: Will not fix

Timeline

  1. 2026-10-02 Threatist record created from CVE-2017-2292
  2. 2026-10-03 Alias added: GHSA-9hgj-f7f3-cph7

References

Sources