Bug 1816722

Summary: CVE-2020-7942 puppet: Arbitrary catalog retrieval [openstack-rdo]
Product: [Community] RDO Reporter: Pedro Sampaio <psampaio>
Component: distributionAssignee: Alfredo Moralejo <amoralej>
Status: CLOSED CURRENTRELEASE QA Contact: Shai Revivo <srevivo>
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: dbecker, jjoyce, jpena, jschluet, lhh, lpeer, markmc, mburns, sclewis, slinaber, srevivo, ykarel
Target Milestone: ---Keywords: Security, SecurityTracking
Target Release: trunk   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: component:puppet
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-28 10:38:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1816720    

Description Pedro Sampaio 2020-03-24 15:35:14 UTC
This is an automatically created tracking bug!  It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of openstack-rdo.

For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.

For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs

When submitting as an update, use the fedpkg template provided in the next
comment(s).  This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.

Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.

Comment 1 Alfredo Moralejo 2020-07-28 10:38:25 UTC
Note this issue only affects when running puppet with a puppet master which is not the case in supported deployment tools in RDO (TripleO, Packstack).

All RDO releases running on CentOS 8 have 6.14.0 which has the fix for this issue.

For previous releases there is a mitigation workaround:

In the puppet.conf configuration file set `strict_hostname_checking = true` on your Puppet master

Closing this issue