This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of fedora-35. 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.
Use the following template to for the 'fedpkg update' request to submit an update for this issue as it contains the top-level parent bug(s) as well as this tracking bug. This will ensure that all associated bugs get updated when new packages are pushed to stable. ===== # bugfix, security, enhancement, newpackage (required) type=security # low, medium, high, urgent (required) severity=medium # testing, stable request=testing # Bug numbers: 1234,9876 bugs=2081181,2083321 # Description of your update notes=Security fix for [PUT CVEs HERE] # Enable request automation based on the stable/unstable karma thresholds autokarma=True stable_karma=3 unstable_karma=-3 # Automatically close bugs when this marked as stable close_bugs=True # Suggest that users restart after update suggest_reboot=False ====== Additionally, you may opt to use the bodhi web interface to submit updates: https://bodhi.fedoraproject.org/updates/new
@amctagga, can you please confirm that this CVE actually affects ansible-collection-community-kubernetes? This seems to be an issue with Openshift itself and not this collection. I was not able to find any relevant information in the collection's changelog or its Github Security Advisories page.
(In reply to Maxwell G from comment #3) > @amctagga, can you please confirm that this CVE actually affects > ansible-collection-community-kubernetes? This seems to be an issue with > Openshift itself and not this collection. I was not able to find any > relevant information in the collection's changelog or its Github Security > Advisories page. According to our analysis and automated tooling, Ansible-Collection-Community-Kubernetes uses openshift, thus we filed a tracker. Hope that helps! (In reply to Maxwell G from comment #2) > @amctagga, can you please confirm that this CVE actually affects > ansible-collection-community-kubernetes? This seems to be an issue with > Openshift itself and not this collection. I was not able to find any > relevant information in the collection's changelog or its Github Security > Advisories page.
Thanks you for your response. > According to our analysis and automated tooling, Ansible-Collection-Community-Kubernetes uses openshift, thus we filed a tracker. Hope that helps! This package doesn't really "use" openshift; it configures it. I don't think there's anything for us to do here, so I'm going to close this as NOTABUG.