LiveActive security incident?Get immediate response
CVE Record

CVE-2017-2295: Versions of Puppet prior to 4.10.1 will deserialize data off the wire (from the agent to the server, in thi...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2017-2295 affects Puppet versions before 4.10.1. A vulnerable Puppet server could be forced to process unsafe YAML data from agent-to-server traffic, potentially allowing remote code execution. For organizations still running these old Puppet versions, this is urgent because Puppet often has broad operational control over managed systems. Exposure is limited to Puppet deployments running versions prior to 4.10.1. The affected surface is Puppet agent-to-server communication. The provided sources do not establish internet exposure, authentication requirements, or whether all deployment modes are equally affected. Prioritize remediation for any legacy Puppet server because successful exploitation could affect infrastructure management. If no pre-4.10.1 Puppet servers remain, residual risk is low. Do not assume active exploitation from the supplied evidence. Mitigation focus: Upgrade Puppet to version 4.10.1 or later.; Review Puppet's CVE advisory for supported remediation guidance.; Apply relevant Debian security updates where Puppet is installed from Debian packages..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-2295 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
PuppetPuppet serverPuppet prior to 4.10.1Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.