Vulnetix
Try Vulnetix Request Demo
CVE-2020-7942 PUBLISHED CVSS 6.5 MEDIUM

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

EPSS 0.12% · 30.7th percentile

Risk Scores

CVSS v3.1
6.5
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS Score
0.12%
30.7th percentile

Affected Products

VendorProductVersions
PuppetPuppet Agent6.x prior to 6.13.0, Fixed in 6.13.0, 5.5.x prior to 5.5.19
puppetpuppet6.0.0, 5.5.0
puppetpuppet_agent6.0.0, 5.5.0
RubyGemspuppet6.0.0, 0
PuppetPuppet6.x prior to 6.13.0, Fixed in 5.5.19, 5.5.x prior to 5.5.19

Timeline

References

Open in Interactive Console →