Advisory

GHSA-gqvf-892r-vjm5

Also known as: CVE-2020-7942

Summary

Improper Certificate Validation in Puppet

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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2021-04-13 15:42 UTC
Modified
2024-02-22 05:39 UTC

Affected packages and fixes

puppet

RubyGems · All systems

Affected

  • introduced 6.0.0, fixed 6.13.0 (ecosystem)

Fixed versions

6.13.0

Fix

The export has no generic command for this ecosystem.

puppet

RubyGems · All systems

Affected

  • introduced 0, fixed 5.5.19 (ecosystem)

Fixed versions

5.5.19

Fix

The export has no generic command for this ecosystem.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences