Loading HuntDB...
Hunt
Vulnerability Intelligence by wss.sh
Home Daily Briefings High Impact CVEs Recent Exploits KEV Catalog GitHub Advisories Latest Updates Security News
Sign In Sign Up

CVE-2020-7942

UNKNOWN
Published 2020-02-19T20:52:03
Actions:

Expert Analysis

Professional remediation guidance

Get tailored security recommendations from our analyst team for CVE-2020-7942. We'll provide specific mitigation strategies based on your environment and risk profile.

No CVSS data available

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

Available Exploits

No exploits available for this CVE.

Related News

No news articles found for this CVE.

Affected Products

Puppet

Puppet

Affected Versions:

5.5.x prior to 5.5.19 Fixed in 5.5.19 6.x prior to 6.13.0 Fixed in 6.13.0
Puppet

Puppet Agent

Affected Versions:

5.5.x prior to 5.5.19 Fixed in 5.5.19 6.x prior to 6.13.0 Fixed in 6.13.0

GitHub Security Advisories

Community-driven vulnerability intelligence from GitHub

✓ GitHub Reviewed MODERATE

Improper Certificate Validation in Puppet

GHSA-gqvf-892r-vjm5

Advisory Details

Previously, Puppet operated on the 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.

Affected Packages

RubyGems puppet
ECOSYSTEM: ≥6.0.0 <6.13.0
RubyGems puppet
ECOSYSTEM: ≥0 <5.5.19

CVSS Scoring

CVSS Score

5.0

CVSS Vector

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

References

ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2020-7942
WEB https://github.com/rubysec/ruby-advisory-db/blob/master/gems/puppet/CVE-2020-7942.yml
WEB https://puppet.com/security/cve/CVE-2020-7942

Advisory provided by GitHub Security Advisory Database. Published: April 13, 2021, Modified: July 5, 2023

References

https://puppet.com/security/cve/CVE-2020-7942/
Published: 2020-02-19T20:52:03
Last Modified: 2024-08-04T09:48:24.553Z
Copied to clipboard!