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 nodes 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

Risk Information

Base Score

6.5

MODERATE

Vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS Score

Exploitation Probability

0.119

Associated Vulnerability

Vulnerability	OS Platform
Vulnerabilities CVE-2020-7942,CVE-2021-27025 are affected in Puppet Agent (x64) 6.12.9	Windows
Vulnerabilities CVE-2020-7942,CVE-2021-27025 are affected in Puppet Agent 6.12.9	Windows
Vulnerabilities CVE-2020-7942 are fixed in Ruby-puppet 6.13.0	Windows
Vulnerabilities CVE-2020-7942 are fixed in Ruby-puppet 5.5.19	Windows
Vulnerabilities CVE-2020-7942 are fixed in Ruby-puppet for Linux 6.13.0	Linux
Vulnerabilities CVE-2020-7942 are fixed in Ruby-puppet for Linux 5.5.19	Linux

Patch Details

No records found

References

https://nvd.nist.gov/vuln/detail/CVE-2023-1234
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-1234