Improper Validation of Certificate with Host Mismatch Affecting foreman-cli package, versions <0:2.1.2.19-1.el7sat


Severity

Recommended
high

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.07% (31st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL7-FOREMANCLI-6582954
  • published7 Apr 2024
  • disclosed18 Feb 2020

Introduced: 18 Feb 2020

CVE-2020-7942  (opens in a new tab)
CWE-297  (opens in a new tab)

How to fix?

Upgrade RHEL:7 foreman-cli to version 0:2.1.2.19-1.el7sat or higher.
This issue was patched in RHSA-2020:4366.

NVD Description

Note: Versions mentioned in the description apply only to the upstream foreman-cli package and not the foreman-cli package as distributed by RHEL. See How to fix? for RHEL:7 relevant fixed versions and status.

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 Scores

version 3.1