CVE-2020-7942
Puppet Certificate Abuse 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
INFO
Published Date :
Feb. 19, 2020, 9:15 p.m.
Last Modified :
Dec. 30, 2021, 1:33 p.m.
Source :
[email protected]
Remotely Exploitable :
Yes !
Impact Score :
3.6
Exploitability Score :
2.8
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2020-7942.
| URL | Resource |
|---|---|
| https://puppet.com/security/cve/CVE-2020-7942/ | Vendor Advisory |
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2020-7942 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2020-7942 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by [email protected]
May. 14, 2024
Action Type Old Value New Value -
Modified Analysis by [email protected]
Dec. 30, 2021
Action Type Old Value New Value Changed CPE Configuration OR *cpe:2.3:a:puppet:puppet:*:*:*:*:*:*:*:* versions from (including) 6.0.0 up to (excluding) 6.13.0 *cpe:2.3:a:puppet:puppet_agent:*:*:*:*:*:*:*:* versions from (including) 6.0.0 up to (excluding) 6.13.0 OR *cpe:2.3:a:puppet:puppet:*:*:*:*:*:*:*:* versions from (including) 5.5.0 up to (excluding) 5.5.19 *cpe:2.3:a:puppet:puppet:*:*:*:*:*:*:*:* versions from (including) 6.0.0 up to (excluding) 6.13.0 *cpe:2.3:a:puppet:puppet_agent:*:*:*:*:*:*:*:* versions from (including) 5.5.0 up to (excluding) 5.5.19 *cpe:2.3:a:puppet:puppet_agent:*:*:*:*:*:*:*:* versions from (including) 6.0.0 up to (excluding) 6.13.0 -
CVE Modified by [email protected]
Apr. 02, 2020
Action Type Old Value New Value Changed 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 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. 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 -
Initial Analysis by [email protected]
Feb. 28, 2020
Action Type Old Value New Value Added CVSS V2 NIST (AV:N/AC:L/Au:S/C:P/I:N/A:N) Added CVSS V3.1 NIST AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N Changed Reference Type https://puppet.com/security/cve/CVE-2020-7942/ No Types Assigned https://puppet.com/security/cve/CVE-2020-7942/ Vendor Advisory Added CWE NIST CWE-295 Added CPE Configuration OR *cpe:2.3:a:puppet:puppet:*:*:*:*:*:*:*:* versions from (including) 6.0.0 up to (excluding) 6.13.0 *cpe:2.3:a:puppet:puppet_agent:*:*:*:*:*:*:*:* versions from (including) 6.0.0 up to (excluding) 6.13.0
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2020-7942 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2020-7942
weaknesses.
Exploit Prediction
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.
0.06 }} 0.00%
score
0.26415
percentile