CVE-2020-7942
Description
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
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
puppetRubyGems | >= 6.0.0, < 6.13.0 | 6.13.0 |
puppetRubyGems | < 5.5.19 | 5.5.19 |
Affected products
2- Range: 5.5.x prior to 5.5.19
- Puppet/Puppet Agentv5Range: 5.5.x prior to 5.5.19
Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
5- github.com/advisories/GHSA-gqvf-892r-vjm5ghsaADVISORY
- nvd.nist.gov/vuln/detail/CVE-2020-7942ghsaADVISORY
- github.com/rubysec/ruby-advisory-db/blob/master/gems/puppet/CVE-2020-7942.ymlghsaWEB
- puppet.com/security/cve/CVE-2020-7942ghsaWEB
- puppet.com/security/cve/CVE-2020-7942/mitrex_refsource_CONFIRM
News mentions
0No linked articles in our index yet.