The Quarterly Threat Landscape Report is out. See what attackers are targeting now.Read report
Previously, Puppet operated on a model that a node with a valid certificate was entitled to all information in the system and that a compromised certificate allowed access to everything in the infrastructure. When a node's catalog falls back to the `default` node, the catalog can be retrieved for a different node by modifying facts for the Puppet run. This issue can be mitigated by setting `strict_hostname_checking = true` in `puppet.conf` on your Puppet master. Puppet 6.13.0 and 5.5.19 changes the default behavior for strict_hostname_checking from false to true. It is recommended that Puppet Open Source and Puppet Enterprise users that are not upgrading still set strict_hostname_checking to true to ensure secure behavior. Affected software versions: Puppet 6.x prior to 6.13.0 Puppet Agent 6.x prior to 6.13.0 Puppet 5.5.x prior to 5.5.19 Puppet Agent 5.5.x prior to 5.5.19 Resolved in: Puppet 6.13.0 Puppet Agent 6.13.0 Puppet 5.5.19 Puppet Agent 5.5.19
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Debian | — | No solution exists | May 15, 2025 | Feb 19, 2020 |
| Freebsd | — | Upgrade puppet6 | Mar 24, 2020 | Mar 23, 2020 |
| Oracle Solaris | — | Upgrade system/management/puppet/oracle-solaris_providers to version 2.0.3-11.4.39.0.1.107.0 on Solaris 11.4 | Nov 17, 2021 | Feb 19, 2020 |
| Suse | — | Upgrade puppet-serverUpgrade puppet | Feb 4, 2022 | Feb 19, 2020 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub