When the module package or service is used and the parameter 'use' is not specified, the module that will be sent to the node is selected by the ansible_fact. If a previous task is executed with a malicious user, the module sent can be selected by the attacker. Additionally, if an Ansible collections are installed the attacker can send the module name to send a reverse shell in temp folder to the node as a binary module.
Acknowledgments: Name: Damien Aumaitre (Quarkslab), Nicolas Surbayrole (Quarkslab)
Borja, is there any upstream reference for this ansible issue?
Created ansible tracking bugs for this issue: Affects: epel-all [bug 1805326] Affects: fedora-all [bug 1805325]
Hey Salvatore, I am working to provide additional information regarding this issue; more details as you requested, affected versions as well as upstream links in case we already have. Prioritising this for now, I will get back to you asap. In reply to comment #4: > Borja, is there any upstream reference for this ansible issue?
Red Hat CloudForms Management Engine 5.9 is in maintenance phase and we're no longer fixing "Low" severity CVEs.
Upstream fix: https://github.com/ansible/ansible/issues/67796
Created ansible tracking bugs for this issue: Affects: openstack-rdo [bug 1807878]
Red Hat Gluster Storage and Red Hat Ceph Storage no longer maintains its own version of Ansible. The fix will be provided from core Ansible. But we still ship ansible separately for ceph ubuntu.
Mitigation: Specify the parameter 'use' when possible on the package and service modules. Avoid using Ansible Collections on Ansible 2.8.9 or 2.7.16 (and any of the previous versions) as they are not rejecting python with no path (already fixed in 2.9.x).
CloudForms 5.11 do not use ansible-tower and 5.10 only using ansible-tower-venv-ansible atm.
Statement: Ansible Engine 2.7.16, 2.8.10, and 2.9.6 as well as previous versions are affected. Ansible Tower 3.4.5, 3.5.5 and 3.6.3 as well as previous versions are affected. In Red Hat OpenStack Platform, because the flaw has a lower impact, ansible is not directly customer exposed, and the fix would require a substantial amount of development, no update will be provided at this time for the RHOSP ansible package.