This page lists changes to the puppet-agent package. For details about changes to components in a puppet-agent release, follow the links to those components in the package release’s notes.
The puppet-agent package’s version numbers use the format X.Y.Z, where:
The puppet-agent package installs the latest version of Puppet 4. Also read the Puppet 4.0 release notes, since they cover any breaking changes since Puppet 3.8.
Also of interest: About Agent, and the Puppet 4.10 release notes.
Released June 13, 2018.
This release of Puppet agent resolves a critical Windows installer bug.
There are no component updates in this Puppet agent release.
The previous version of the Windows Puppet agent installer had an internal MSI property resolution issue that could be triggered when requesting that msiexec install the same version of the Puppet agent package that was already installed on the node. In those rare instances, and when combined with the permission resetting code introduced in PA-2019 as a response to CVE-2018-6513, the Puppet agent package could execute takeown.exe and icacls.exe against the filesystem root (C:\), resulting in incorrectly rewritten permissions across the filesystem.
Using the Chocolatey package provider to perform an in-place upgrade of the Puppet package during a Puppet run, which is the workflow used by Foreman, most commonly triggered this behavior.
Puppet agent 1.10.14 resolves both of these problems by implementing a workaround of the MSI property resolution issue and making the PA-2019 permission resetting code more defensive. (PA-2075)
In Puppet agent 1.10.13, Puppet’s systemd services were not always enabled as expected on Debian and derivative operating systems, such as within the debian-installer chroot. This could lead to Puppet services being disabled after an automated deployment of agent 1.10.13 on these operating systems. Puppet agent 1.10.14 fixes this regression. (PA-2072)
Released June 7, 2018.
This release of Puppet agent includes bug fixes and security updates.
This release updates Puppet to Puppet 4.10.12.
Previous versions of Puppet on Ruby 2.0 or newer would close and reopen HTTP connection that were idle for more than 2 seconds, causing increased load on Puppet masters. This version of Puppet ensures that the agent uses the http_keepalive_timeout setting when determining when to close idle connections. (PUP-8663)
When installing or updating puppet-agent 1.10.12, it updates the MANPATH environment variable so that Puppet’s man pages are available. (PA-1847)
On Windows, Puppet no longer includes /opt/puppetlabs/puppet/modules in its default basemodulepath, because unprivileged users could create a C:\opt directory and escalate privileges. (PUP-8707)
This version of Puppet agent restricts permissions to some directories within C:\ProgramData\PuppetLabs so that only LocalSystem and members of the local Administrators group have access. (PA-2019)
Released April 17, 2018.
There was no public Puppet agent 1.10.11 release.
This release contains bug fixes in Puppet 4.10.11, Facter 3.6.10, Hiera 3.3.3, and pxp-agent 1.5.7. It also updates virt-what to version 1.18 on Linux platforms.
Updates curl to version 7.59.0. (PA-1913)
This release includes fixes for the following security vulnerabilities in Ruby: (PA-1959)
The puppet-agent package no longer invokes custom facts on upgrade, avoiding a deadlock when such a fact tried to access the package manager’s database. (PA-1402)
Resolved an issue that prevented locales from appearing. (PA-1850)
All of the Dynamic Link Library (dll) files required by the pxp-agent binary are copied to the executable’s directory (<pxp-agent-install-root>/bin). (PA-1908)
Update virt-what from version 1.14 to version 1.18 (only affects linux platforms) (PA-1893)
MCollective now relies only on its internal log rotation rather than also using the logrotate configuration. This prevents conflicting rotations and simplifies configuration. (PA-1823)
Log rotation under systemd correctly signals pxp-agent to re-open the log file. (PCP-834)
Released February 5, 2018.
This release contains bug fixes in Puppet 4.10.10 and Facter 3.6.9.
This release adds packages for RHEL 7 on ARM and macOS 10.13 High Sierra.
Released November 6, 2017.
This release contains bug fixes in Puppet 4.10.9, Facter 3.6.8, and MCollective 2.10.6, updates its vendored cURL to v7.56.1, and updates its certificate authority (CA) certificate bundle.
This release also updates Puppet’s vendored Ruby to version 2.1.9, which addresses the following security vulnerabilities:
It also updates rubygems to version 2.6.13, which addresses the following security vulnerabilities:
When running Facter from previous versions of the Puppet agent package on a machine with a Power8 architecture, dmesg would produce an error message:
Program dmidecode tried to access /dev/mem between f0000->100000.
Puppet agent 1.10.9 resolves this issue by not including a vendored dmidecode in packages targeting Power8 architectures.
mcollective service is no longer configured to kill all child processes when stopped under systemd. It will now only kill the mcollective service, letting agent subprocesses continue to completion. As a result, MCollective can now upgrade puppet-agent.Released September 14, 2017.
This release contains a bug fix in Puppet 4.10.8 and a versioning fix in the Windows package. No other components are updated.
Previous versions of Puppet agent did not increment the version of NSSM in a manner expected by Microsoft Installer (MSI), leading to MSI unintentionally removing it upon upgrade. Puppet agent 1.10.8 resolves this issue by changing the versioning scheme for NSSM.
Released September 6, 2017.
This release contains a security improvement in the Windows package, and bug fixes in Puppet 4.10.7, Facter 3.6.7, and pxp-agent 1.5.5.
pxp-agentAs part of security robustness measure, this version of the puppet-agent package for Windows enables data execution prevention (aka /NX) and address space layout randomization (ASLR) in third-party binaries, such as Ruby and OpenSSL, that are built along with Puppet Agent modules. There was no specific known vulnerability, but this improvement prevents potential exploits using the above concerns as attack vectors.
Released August 9, 2017.
The only component update in this Puppet agent release is Puppet 4.10.6.
These platforms have been added as of Puppet agent 1.10.6:
Released July 26, 2017.
This release contains bug fixes in Puppet 4.10.5, and Facter 3.6.6 and pxp-agent 1.5.4.
These platforms have been added as of Puppet agent 1.10.5:
Released June 19, 2017.
This release only affects Puppet. A regression in Puppet 4.10.3 where resources created using the syntax Resource[xx::yy] would cause an error because Puppet would not find an existing xx::yy user defined resource type. This was caused by fixing another problem with inconsistent use of upper and lowercase in references.
Released June 15, 2017.
This release only affects Puppet. Using ampersands (&) in custom facts was causing Puppet runs to fail in Puppet 4.10.2. This release includes Puppet 4.10.3, which resolves that issue.
Released June 12, 2017.
This is a bug fix release with updates to several components, including Puppet 4.10.2, Facter 3.6.5, Hiera 3.3.2, MCollective 2.10.5, and pxp-agent 1.5.3.
Released May 11, 2017.
This is a security release with an update to OpenSSL 1.0.2k, and also includes bug fixes for Puppet 4.10.1, MCollective 2.10.4, and Facter 3.6.4.
An authenticated agent could make a catalog request with facts encoded in YAML. The Puppet master did not properly validate and reject the request, resulting in the server loading arbitrary objects, which could lead to remote code execution. (PUP-7483)
As of the Puppet agent 1.10.1 release, we no longer ship packages for EL 4, Fedora 23, and Ubuntu 12.04.
Released April 5, 2017.
Components with updates in this release are Puppet 4.10.0, Facter 3.6.3, MCollective 2.10.3, and pxp-agent 1.5.0.
The largest updates in this release include improvements and bug fixes for Hiera 5, which ships with Puppet 4.10.
pxp-agent new featurepxp-agent Now responds to PXP non-blocking requests that use a duplicate transaction ID by sending a provisional response, rather than an error message. Status requests can then be sent as normal to check on the status of the original request that was duplicated. It also detects duplicate IDs that are stored on-disk, rather than only those in-memory (it no longer “forgets” when the process is restarted). (PCP-627)
pxp-agent bug fixThe default ping interval has been increased to two minutes to reduce disconnect and reconnect cycling against a heavily loaded broker. This has a side effect that failover when a connection is unavailable but the TCP connection was not properly closed now takes 4-6 minutes instead of 35-50 seconds. (PCP-729)