Back

HIGH

puppet: puppet server and puppetDB may leak sensitive information via metrics API

Published Mar 11, 2020

Description

Puppet Server and PuppetDB provide useful performance and debugging information via their metrics API endpoints. For PuppetDB this may contain things like hostnames. Puppet Server reports resource names and titles for defined types (which may contain sensitive information) as well as function names and class names. Previously, these endpoints were open to the local network. PE 2018.1.13 & 2019.5.0, Puppet Server 6.9.2 & 5.3.12, and PuppetDB 6.9.1 & 5.2.13 disable trapperkeeper-metrics /v1 metrics API and only allows /v2 access on localhost by default. This affects software versions: Puppet Enterprise 2018.1.x stream prior to 2018.1.13 Puppet Enterprise prior to 2019.5.0 Puppet Server prior to 6.9.2 Puppet Server prior to 5.3.12 PuppetDB prior to 6.9.1 PuppetDB prior to 5.2.13 Resolved in: Puppet Enterprise 2018.1.13 Puppet Enterprise 2019.5.0 Puppet Server 6.9.2 Puppet Server 5.3.12 PuppetDB 6.9.1 PuppetDB 5.2.13

Affected products

Remediation

Red Hat statement

No releases of Red Hat OpenStack Platform are affected as they do not provide Puppet Server or PuppetDB.

Red Hat mitigation

Disable the trapperkeeper-metrics /v1 metrics API

References (5)

Change history (0)

No recorded changes yet.

Sources
CVE.org / MITRE
Status PUBLISHED
Assigner puppet
Published Mar 11, 2020
Updated Aug 4, 2024
Reserved Jan 23, 2020
NVD
Status Modified
Modified Jun 17, 2026
Red Hat
Severity Important
Public date Mar 10, 2020