Ansible before version 2.2.0 fails to properly sanitize fact variables sent from the Ansible controller. An attacker with the ability to create special variables on the controller could execute arbitrary commands on Ansible clients as the user Ansible runs as.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - Ansible before version 2.2.0 fails to properly sanitize fact variables sent from the Ansible controller.
    An attacker with the ability to create special variables on the controller could execute arbitrary     commands on Ansible clients as the user Ansible runs as. (CVE-2016-8628)

Note that Nessus relies on the presence of the package as reported by the vendor.

The remote SUSE Linux SLES15 / openSUSE 15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2024:1509-1 advisory.

  - A flaw was found in Ansible before version 2.2.0. The apt_key module does not properly verify key     fingerprints, allowing remote adversary to create an OpenPGP key which matches the short key ID and inject     this key instead of the correct key. (CVE-2016-8614)

  - Ansible before version 2.2.0 fails to properly sanitize fact variables sent from the Ansible controller.
    An attacker with the ability to create special variables on the controller could execute arbitrary     commands on Ansible clients as the user Ansible runs as. (CVE-2016-8628)

  - An input validation vulnerability was found in Ansible's mysql_user module before 2.2.1.0, which may fail     to correctly change a password in certain circumstances. Thus the previous password would still be active     when it should have been changed. (CVE-2016-8647)

  - Ansible before versions 2.1.4, 2.2.1 is vulnerable to an improper input validation in Ansible's handling     of data sent from client systems. An attacker with control over a client system being managed by Ansible     and the ability to send facts back to the Ansible server could use this flaw to execute arbitrary code on     the Ansible server using the Ansible server privileges. (CVE-2016-9587)

  - A flaw was found in the way Ansible (2.3.x before 2.3.3, and 2.4.x before 2.4.1) passed certain parameters     to the jenkins_plugin module. Remote attackers could use this flaw to expose sensitive information from a     remote host's logs. This flaw was fixed by not allowing passwords to be specified in the params     argument, and noting this in the module documentation. (CVE-2017-7550)

  - In ansible it was found that inventory variables are loaded from current working directory when running     ad-hoc command which are under attacker's control, allowing to run arbitrary code as a result.
    (CVE-2018-10874)

  - An incomplete fix was found for the fix of the flaw CVE-2020-1733 ansible: insecure temporary directory     when running become_user from become directive. The provided fix is insufficient to prevent the race     condition on systems using ACLs and FUSE filesystems. Ansible Engine 2.7.18, 2.8.12, and 2.9.9 as well as     previous versions are affected and Ansible Tower 3.4.5, 3.5.6 and 3.6.4 as well as previous versions are     affected. (CVE-2020-10744)

  - An Improper Output Neutralization for Logs flaw was found in Ansible when using the uri module, where     sensitive data is exposed to content and json output. This flaw allows an attacker to access the logs or     outputs of performed tasks to read keys used in playbooks from other users within the uri module. The     highest threat from this vulnerability is to data confidentiality. (CVE-2020-14330)

  - A flaw was found in the Ansible Engine when using module_args. Tasks executed with check mode (--check-     mode) do not properly neutralize sensitive data exposed in the event data. This flaw allows unauthorized     users to read this data. The highest threat from this vulnerability is to confidentiality.
    (CVE-2020-14332)

  - A flaw was found in the Ansible Engine, in ansible-engine 2.8.x before 2.8.15 and ansible-engine 2.9.x     before 2.9.13, when installing packages using the dnf module. GPG signatures are ignored during     installation even when disable_gpg_check is set to False, which is the default behavior. This flaw leads     to malicious packages being installed on the system and arbitrary code executed via package installation     scripts. The highest threat from this vulnerability is to integrity and system availability.
    (CVE-2020-14365)

  - A security flaw was found in Ansible Engine, all Ansible 2.7.x versions prior to 2.7.17, all Ansible 2.8.x     versions prior to 2.8.11 and all Ansible 2.9.x versions prior to 2.9.7, when managing kubernetes using the     k8s module. Sensitive parameters such as passwords and tokens are passed to kubectl from the command line,     not using an environment variable or an input configuration file. This will disclose passwords and tokens     from process list and no_log directive from debug module would not have any effect making these secrets     being disclosed on stdout and log files. (CVE-2020-1753)

  - A template injection flaw was found in Ansible where a user's controller internal templating operations     may remove the unsafe designation from template data. This issue could allow an attacker to use a     specially crafted file to introduce templating injection when supplying templating data. (CVE-2023-5764)

  - A user changing their email after signing up and verifying it can change it without verification in     profile settings. The configuration option verify_email_enabled will only validate email only on sign     up. (CVE-2023-6152)

  - An information disclosure flaw was found in ansible-core due to a failure to respect the ANSIBLE_NO_LOG     configuration in some scenarios. Information is still included in the output in certain tasks, such as     loop items. Depending on the task, this issue may include sensitive information, such as decrypted secret     values. (CVE-2024-0690)

  - It is possible for a user in a different organization from the owner of a snapshot to bypass authorization     and delete a snapshot by issuing a DELETE request to /api/snapshots/<key> using its view key. This     functionality is intended to only be available to individuals with the permission to write/edit to the     snapshot in question, but due to a bug in the authorization logic, deletion requests issued by an     unprivileged user in a different organization than the snapshot owner are treated as authorized. Grafana     Labs would like to thank Ravid Mazon and Jay Chen of Palo Alto Research for discovering and disclosing     this vulnerability. This issue affects Grafana: from 9.5.0 before 9.5.18, from 10.0.0 before 10.0.13, from     10.1.0 before 10.1.9, from 10.2.0 before 10.2.6, from 10.3.0 before 10.3.5. (CVE-2024-1313)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Redhat Enterprise Linux 7 host has packages installed that are affected by a vulnerability as referenced in the RHSA-2016:2778 advisory.

    Red Hat OpenShift Container Platform is the company's cloud computing Platform-as-a-Service (PaaS)     solution designed for on-premise or private cloud deployments.

    Security Fix(es):

    * Ansible fails to properly sanitize fact variables sent from the Ansible controller. An attacker with the     ability to create special variables on the controller could execute arbitrary commands on Ansible clients     as the user Ansible runs as. (CVE-2016-8628)

    This issue was discovered by Michael Scherer (Red Hat).

    Bug Fix(es):

    * Previous versions of the openshift-ansible code base were not compatible with the latest Ansible 2.2.0.0     release. This bug fix resolves several compatibility issues with the GA version of Ansible 2.2.0.0.
    (BZ#1389928) (BZ#1389275)

    * The hosts.ose.example inventory file had the incorrect openshift_release version set. This bug fix     updates the version to match the channel in which it is shipped. (BZ#1386333)

    * The etcd certificate authority created by the installer had an expiry date one year in the future. With     this bug fix, the expiry date has been updated to five years, matching the lifespan of other certificate     authorities created by the installer. (BZ#1391548)

    * After restarting systemd-journal, master controllers and API services stopped working. This bug fix     updates the installer to set Restart=always for the master controllers and API services, and this issue no     longer occurs for new installations. For existing clusters, see     https://access.redhat.com/solutions/2749571. (BZ#1378929)

    * When using the quick installer to install a cluster with a single master, the installer messaging     suggested that an embedded etcd would be deployed. In newer versions of the quick installer, this is no     longer the case, and a stand-alone etcd datastore is deployed in this scenario. This bug fix updates the     quick installer messaging to match those changes. (BZ#1383961)

    * Upgrades would fail if the /etc/ansible/facts.d/openshift.fact cache was missing on the system,     particularly for co-located master and etcd hosts. This bug fix improves etcd fact checking during     upgrades, and the issue no longer occurs. (BZ#1391608)

    * Containerized upgrades from OpenShift Container Platform 3.2 to 3.3 would fail to properly create the     service signing certificate due to an invalid path being used in containerized environments. This bug fix     corrects that error, and containerized upgrades now create service signer certificates as a result.
    (BZ#1391865)

    * Upgrades from OpenShift Container Platform 3.2 to 3.3 could fail with the error     AnsibleUndefinedVariable: 'dict object' has no attribute 'debug_level'. This bug fix sets missing     defaults for debug_level, and as a result the upgrade error no longer occurs. (BZ#1392276)

    * Previously in embedded environments, etcd 2.x was used to backup the etcd data before performing an     upgrade. However, etcd 2.x has a bug that prevents backups from working properly, preventing the upgrade     playbooks from running to completion. With this bug fix, etcd 3.0 is now installed for embedded etcd     environments, which resolves the bug allowing upgrades to proceed normally. This bug only presents itself     when using the embedded etcd service on single master environments. (BZ#1382634)

    * Pacemaker clusters are no longer supported, but related code that remained could in some cases cause     upgrade failures. This bug fix removes the Pacemaker restart logic from the installer to avoid these     issues. (BZ#1382936)

    * Previously, upgrades from OpenShift Container Platform 3.1 to 3.2 could fail due to erroneous host names     being added for etcd hosts during backup. This bug fix addresses issues with conditionals and loops in     templates that caused this problem, and as a result the upgrade errors no longer occur. (BZ#1392169)

    All OpenShift Container Platform users are advised to upgrade to these updated packages.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

This update for ansible to version 2.4.1.0 fixes the following vulnerabilities :

  - CVE-2017-7481: Security issue with lookup return not     tainting the jinja2 environment (bsc#1038785)

  - CVE-2016-9587: host to controller command execution     vulnerability (bsc#1019021)

  - CVE-2016-8628: Command injection by compromised server     via fact variables (bsc#1008037)

  - CVE-2016-8614: Improper verification of key fingerprints     in apt_key module (bsc#1008038)

  - CVE-2017-7550: jenkins_plugin module may have exposed     passwords in remote host logs (bsc#1065872)

This update also contains a number of upstream bug fixes and improvements.

Add patch to fix dnf module groupinstall handling

----

Update to new ansible 2.2 version. 

For full changes see :

https://github.com/ansible/ansible/blob/stable-2.2/CHANGELOG.md

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website.
Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

ID	Name	Product	Family	Severity
219768	Linux Distros Unpatched Vulnerability : CVE-2016-8628	Nessus	Misc.	critical
195097	SUSE SLES15 / openSUSE 15 Security Update : SUSE Manager Client Tools (SUSE-SU-2024:1509-1)	Nessus	SuSE Local Security Checks	critical
119385	RHEL 7 : atomic-openshift-utils (RHSA-2016:2778)	Nessus	Red Hat Local Security Checks	critical
104522	openSUSE Security Update : ansible (openSUSE-2017-1259)	Nessus	SuSE Local Security Checks	critical
94999	Fedora 25 : ansible (2016-3ccb098630)	Nessus	Fedora Local Security Checks	critical
94614	Fedora 24 : ansible (2016-3113e71193)	Nessus	Fedora Local Security Checks	critical

Detections

Analytics

CVE-2016-8628

critical

Tenable Plugins

critical

critical

critical

critical

critical

critical