Vulnerability 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
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Puppet | Puppet | >= 5.5.0, < 5.5.19 |
| Puppet | Puppet Agent | >= 5.5.0, < 5.5.19 |
Related Weaknesses (CWE)
References
- https://puppet.com/security/cve/CVE-2020-7942/Vendor Advisory
- https://puppet.com/security/cve/CVE-2020-7942/Vendor Advisory
FAQ
What is CVE-2020-7942?
CVE-2020-7942 is a vulnerability with a CVSS score of 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 infrast...
How severe is CVE-2020-7942?
CVE-2020-7942 has been rated MEDIUM with a CVSS base score of 6.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2020-7942?
Check the references section above for vendor advisories and patch information. Affected products include: Puppet Puppet, Puppet Puppet Agent.