Previously, Puppet operated on the 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 changes the default behavior for stricthostnamechecking from false to true. It is recommended that Puppet Open Source and Puppet Enterprise users that are not upgrading still set stricthostnamechecking to true to ensure secure behavior.
{
"github_reviewed_at": "2021-04-07T23:15:22Z",
"cwe_ids": [
"CWE-295"
],
"nvd_published_at": "2020-02-19T21:15:00Z",
"github_reviewed": true,
"severity": "MODERATE"
}