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

Published: 2017-06-30 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2017-2292 is rated Moderate Risk (64.4/100): CVSS Critical severity, with medium exploitation likelihood (EPSS 2.18%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2017-2292

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 1.80% 2.18% +0.38%
2 2026-03-03 1.93% 1.80% -0.13%
3 2025-03-30 — 1.93% —

Full EPSS history (10 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2017-2292

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.0 3.0 CRITICAL
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 2.3 6.0 [email protected]
7.5 2.0 HIGH
AV:N/AC:L/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 10.0 6.4 [email protected]

Weakness enumeration for CVE-2017-2292

OS Trackers for CVE-2017-2292

vendor priority summary link
debian not yet assigned CVE-2017-2292 not yet assigned priority: Debian including 1 source packages (mcollective), 2 status rows across 2 suites (bookworm, bullseye): resolved 2. https://security-tracker.debian.org/tracker/CVE-2017-2292
gentoo normal CVE-2017-2292: 1 GLSA(s) (201709-01), 1 atom(s) (app-admin/mcollective); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2017-2292
redhat high — https://access.redhat.com/security/cve/CVE-2017-2292
ubuntu medium CVE-2017-2292 medium priority: Ubuntu including 1 source packages (mcollective), 22 status rows across 22 suites (artful, bionic, cosmic, disco, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial, yakkety, zesty): not-affected 14, ignored 3, DNE 2, needed 2, released 1. https://ubuntu.com/security/CVE-2017-2292

Affected software / configurations for CVE-2017-2292

Vendor Product Version Raw CPE
puppet mcollective <= 2.10.3 cpe:2.3:a:puppet:mcollective:*:*:*:*:*:puppet:*:*

References for CVE-2017-2292

cvelogic Threat Intelligence