CVE-2017-2295

Versions of Puppet prior to 4.10.1 will deserialize data off the wire (from the agent to the server, in this case) with a attacker-specified format. This could be used to force YAML deserialization in an unsafe manner, which would lead to remote code execution. This change constrains the format of data on the wire to PSON or safely decoded YAML.

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

CVE-2017-2295 is rated Moderate Risk (60.7/100): CVSS High severity, with medium exploitation likelihood (EPSS 1.45%). 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-2295

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-05-13 1.89% 1.45% -0.44%
2 2026-03-08 1.96% 1.89% -0.07%
3 2025-03-30 — 1.96% —

Full EPSS history (10 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.2 3.0 HIGH
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N 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:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
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:N)
Service keeps running; no real outage angle.
 1.8 5.8 [email protected]
6.0 2.0 MEDIUM
AV:N/AC:M/Au:S/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:S)
A single authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 6.8 6.4 [email protected]

Weakness enumeration for CVE-2017-2295

OS Trackers for CVE-2017-2295

vendor priority summary link
debian not yet assigned CVE-2017-2295 not yet assigned priority: Debian including 1 source packages (puppet), 1 status rows across 1 suites (bullseye): resolved 1. https://security-tracker.debian.org/tracker/CVE-2017-2295
redhat high — https://access.redhat.com/security/cve/CVE-2017-2295
suse high — https://www.suse.com/security/cve/CVE-2017-2295/
ubuntu medium CVE-2017-2295 medium priority: Ubuntu including 1 source packages (puppet), 15 status rows across 15 suites (artful, bionic, cosmic, disco, eoan, focal, groovy, hirsute, impish, jammy, trusty, upstream, xenial, yakkety, zesty): not-affected 10, released 3, ignored 2. https://ubuntu.com/security/CVE-2017-2295

Affected software / configurations for CVE-2017-2295

Vendor Product Version Raw CPE
puppet puppet <= 4.10.0 cpe:2.3:a:puppet:puppet:*:*:*:*:*:*:*:*
debian debian_linux 8.0 cpe:2.3:o:debian:debian_linux:8.0:*:*:*:*:*:*:*

References for CVE-2017-2295

cvelogic Threat Intelligence