CVE-2017-2292: Versions of MCollective prior to 2.10.4 deserialized YAML from agents without calling safe_load, allowing the

Q: How do I fix CVE-2017-2292?

mcollective: upgrade to newer than 2.10.3. Exact commands for each OS are on this page.

Q: Is CVE-2017-2292 being exploited?

CVE-2017-2292 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2017-2292 affect?

CVE-2017-2292 affects mcollective. Severity is critical (CVSS 9.0). 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

Q: How urgent is CVE-2017-2292?

Priority 52/100. Critical severity

This month

CRITICAL 9.0UPGRADE

CVE-2017-2292 is a critical-severity flaw (CVSS 9.0) affecting mcollective. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 this priority

Critical severity

A fixed release or distro patch exists.

Risk facts

CVSS score	9.0 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	None
EPSS exploit chance	2.2% (top 18%)
CISA exploited list	No
Weakness	CWE-502
Published	2017-06-30
Last modified	2026-06-17

Publisher (CNA): Perforce · Vendor: puppet

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2017-06-30 20:29 UTCPublished CVE record published
2026-06-17 01:15 UTCUpdated Record last modified

puppet mcollective UPGRADE

Affected: <= 2.10.3

Fixed in: newer than 2.10.3

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy mcollective || rpm -q mcollective || mcollective --version

2. UPGRADE to newer than 2.10.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade mcollective

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade mcollective

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-2292?

mcollective: upgrade to newer than 2.10.3. Exact commands for each OS are on this page.

Is CVE-2017-2292 being exploited?

CVE-2017-2292 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-2292 affect?

CVE-2017-2292 affects mcollective. Severity is critical (CVSS 9.0). 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

How urgent is CVE-2017-2292?

Priority 52/100. Critical severity

Related CVEs

CVE-2014-3251 MEDIUM 4.4 UPGRADE MITIGATE The MCollective aes_security plugin, as used in Puppet Enterprise before 3.3.0 and Mcollective before 2.5.3, d

References

← Back to latest CVEs