Bug 1828486 (CVE-2020-7943) - CVE-2020-7943 puppet: puppet server and puppetDB may leak sensitive information via metrics API
Summary: CVE-2020-7943 puppet: puppet server and puppetDB may leak sensitive informati...
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2020-7943
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1828729
Blocks: 1827749
TreeView+ depends on / blocked
 
Reported: 2020-04-27 19:55 UTC by Guilherme de Almeida Suckevicz
Modified: 2021-12-14 18:47 UTC (History)
25 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
A flaw was found where the metrics API endpoints of Puppet Server and PuppetDB leaked sensitive information to the local network. Listening to these network endpoints could allow attackers the ability to exploit additional computer systems. The highest impact of this flaw is confidentiality.
Clone Of:
Environment:
Last Closed: 2020-10-27 14:21:31 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:4366 0 None None None 2020-10-27 12:56:41 UTC

Description Guilherme de Almeida Suckevicz 2020-04-27 19:55:47 UTC 
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

Reference:
https://puppet.com/security/cve/CVE-2020-7943/
Comment 3 Yadnyawalk Tale 2020-04-28 09:24:58 UTC 
External References:

https://puppet.com/security/cve/CVE-2020-7943
Comment 4 Riccardo Schirone 2020-04-29 12:48:25 UTC 
The fix seems to be:
https://github.com/puppetlabs/puppet_metrics_dashboard/commit/9c4ce53dc642a7aaa2e6cc960d00cc4e79558870

Which comes from the following PR:
https://github.com/puppetlabs/puppet_metrics_dashboard/pull/92
Comment 6 Breno 2020-04-29 13:50:21 UTC 
FYI, AFAIK,

We don't have/support puppetserver [1].

Puppet 5 is the last version of puppet that included puppet master, which is a different thing, not actually puppet server.

1 https://github.com/puppetlabs/puppetserver
Comment 8 Nick Tait 2020-04-29 21:10:15 UTC 
Mitigation:

Disable the trapperkeeper-metrics /v1 metrics API
Comment 9 Nick Tait 2020-04-30 19:45:25 UTC 
Statement:

No releases of Red Hat OpenStack Platform are affected as they do not provide Puppet Server or PuppetDB.
Comment 10 errata-xmlrpc 2020-10-27 12:56:36 UTC 
This issue has been addressed in the following products:

  Red Hat Satellite 6.7 for RHEL 8

Via RHSA-2020:4366 https://access.redhat.com/errata/RHSA-2020:4366
Comment 11 Product Security DevOps Team 2020-10-27 14:21:31 UTC 
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2020-7943
Note You need to log in before you can comment on or make changes to this bug.