CVE-2020-7942

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

• CVE ID
• CVE-2020-7942

• Assigner
• security@puppet.com

• Vulnerability Status
• Analyzed

• Published Version
• 2020-02-19T21:15:11

• Last Modified Date
• 2021-12-30T13:33:51

• Version
• 2.0

• Vector String
• AV:N/AC:L/Au:S/C:P/I:N/A:N

• Access Vector
• NETWORK

• Access Compatibility
• LOW

• Authentication
• SINGLE

• Confidentiality Impact
• PARTIAL

• Integrity Impact
• NONE

• Availability Impact
• NONE

• Base Score
• 4

• Severity
• MEDIUM

• Exploitability Score
• 8

• Impact Score
• 2.9

• Version
• 3.1

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

• Attack Vector
• NETWORK

• Attack Compatibility
• LOW

• Privileges Required
• LOW

• User Interaction
• NONE

• Scope
• UNCHANGED

• Confidentiality Impact
• HIGH

• Availability Impact
• NONE

• Base Score
• 6.5

• Base Severity
• MEDIUM

• Exploitability Score
• 2.8

• Impact Score
• 3.6