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.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - 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)

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.

    POS_Image-Graphical7 was updated to version 0.1.1710765237.46af599:

    - Version 0.1.1710765237.46af599

      * Moved image services to dracut-saltboot package
      * Use salt bundle

    - Version 0.1.1645440615.7f1328c

      * Removed deprecated kiwi functions

    POS_Image-JeOS7 was updated to version 0.1.1710765237.46af599:

    - Version 0.1.1710765237.46af599

      * Moved image services to dracut-saltboot package
      * Use salt bundle

    - Version 0.1.1645440615.7f1328c

      * Removed deprecated kiwi functions

    ansible received the following fixes:

    - Security issues fixed:

      * CVE-2023-5764: Address issues where internal templating can cause unsafe         variables to lose their unsafe designation (bsc#1216854)

        - Breaking changes:
          assert - Nested templating may result in an inability for the conditional           to be evaluated. See the porting guide for more information.

      * CVE-2024-0690: Address issue where ANSIBLE_NO_LOG was ignored (bsc#1219002)
      * CVE-2020-14365: Ensure that packages are GPG validated (bsc#1175993)
      * CVE-2020-10744: Fixed insecure temporary directory creation (bsc#1171823)
      * CVE-2018-10874: Fixed inventory variables loading from current working directory when running ad-hoc     command that         can lead to code execution (bsc#1099805)

    - Bugs fixed:

      * Don't Require python-coverage, it is needed only for testing (bsc#1177948)

    dracut-saltboot was updated to version 0.1.1710765237.46af599:

    - Version 0.1.1710765237.46af599

      * Load only first available leaseinfo (bsc#1221092)

    - Version 0.1.1681904360.84ef141

    grafana was updated to version 9.5.18:

    - Grafana now requires Go 1.20
    - Security issues fixed:

      * CVE-2024-1313: Require same organisation when deleting snapshots (bsc#1222155)
      * CVE-2023-6152: Add email verification when updating user email (bsc#1219912)

    - Other non-security related changes:

      * Version 9.5.17:

        - [FEATURE] Alerting: Backport use Alertmanager API v2

      * Version 9.5.16:

        - [BUGFIX] Annotations: Split cleanup into separate queries and           deletes to avoid deadlocks on MySQL

      * Version 9.5.15:

        - [FEATURE] Alerting: Attempt to retry retryable errors

      * Version 9.5.14:

        - [BUGFIX] Alerting: Fix state manager to not keep           datasource_uid and ref_id labels in state after Error
        - [BUGFIX] Transformations: Config overrides being lost when           config from query transform is applied
        - [BUGFIX] LDAP: Fix enable users on successfull login

      * Version 9.5.13:

        - [BUGFIX] BrowseDashboards: Only remember the most recent           expanded folder
        - [BUGFIX] Licensing: Pass func to update env variables when           starting plugin

      * Version 9.5.12:

        - [FEATURE] Azure: Add support for Workload Identity           authentication

      * Version 9.5.9:

        - [FEATURE] SSE: Fix DSNode to not panic when response has empty           response
        - [FEATURE] Prometheus: Handle the response with different field           key order
        - [BUGFIX] LDAP: Fix user disabling

    mgr-daemon was updated to version 4.3.9-0:

    - Version 4.3.9-0

      * Update translation strings

    spacecmd was updated to version 4.3.27-0:

    - Version 4.3.27-0

      * Update translation strings

    spacewalk-client-tools was updated to version 4.3.19-0:

    - Version 4.3.19-0

      * Update translation strings

    spacewalk-koan was updated to version version 4.3.6-0:

    - Version 4.3.6-0

      * Change Docker image location for test

    uyuni-common-libs was updated to version 4.3.10-0:

    - Version 4.3.10-0

      * Add support for package signature type V4 RSA/SHA384
      * Add support for package signature type V4 RSA/SHA512 (bsc#1221465)

    uyuni-proxy-systemd-services was updated to version 4.3.12-0:

    - Version 4.3.12-0

      * Update to SUSE Manager 4.3.12

Tenable has extracted the preceding description block directly from the SUSE security advisory.

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
421963	SCA: security update for ansible (GHSA-jg4f-jqm5-4mgq)	Tenable Cloud Security	SCA Checks	critical
421963	SCA: security update for ansible (GHSA-jg4f-jqm5-4mgq)	Tenable Self-Hosted Container Security	SCA Checks	critical
195097	SUSE SLES15: POS_Image-Graphical7 / POS_Image-JeOS7 / ansible / ansible-doc / etc (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

critical