Ansible, versions 2.9.x before 2.9.1, 2.8.x before 2.8.7 and Ansible versions 2.7.x before 2.7.15, is not respecting the flag no_log set it to True when Sumologic and Splunk callback plugins are used send tasks results events to collectors. This would discloses and collects any sensitive data.

The remote Debian 10 host has packages installed that are affected by multiple vulnerabilities as referenced in the dsa-4950 advisory.

  - A flaw was discovered in the way Ansible templating was implemented in versions before 2.6.18, 2.7.12 and     2.8.2, causing the possibility of information disclosure through unexpected variable substitution. By     taking advantage of unintended variable substitution the content of any variable may be disclosed.
    (CVE-2019-10156)

  - ansible-playbook -k and ansible cli tools, all versions 2.8.x before 2.8.4, all 2.7.x before 2.7.13 and     all 2.6.x before 2.6.19, prompt passwords by expanding them from templates as they could contain special     characters. Passwords should be wrapped to prevent templates trigger and exposing them. (CVE-2019-10206)

  - In Ansible, all Ansible Engine versions up to ansible-engine 2.8.5, ansible-engine 2.7.13, ansible-engine     2.6.19, were logging at the DEBUG level which lead to a disclosure of credentials if a plugin used a     library that logged credentials at the DEBUG level. This flaw does not affect Ansible modules, as those     are executed in a separate process. (CVE-2019-14846)

  - Ansible, versions 2.9.x before 2.9.1, 2.8.x before 2.8.7 and Ansible versions 2.7.x before 2.7.15, is not     respecting the flag no_log set it to True when Sumologic and Splunk callback plugins are used send tasks     results events to collectors. This would discloses and collects any sensitive data. (CVE-2019-14864)

  - A flaw was found in the solaris_zone module from the Ansible Community modules. When setting the name for     the zone on the Solaris host, the zone name is checked by listing the process with the 'ps' bare command     on the remote machine. An attacker could take advantage of this flaw by crafting the name of the zone and     executing arbitrary commands in the remote host. Ansible Engine 2.7.15, 2.8.7, and 2.9.2 as well as     previous versions are affected. (CVE-2019-14904)

  - A flaw was found in Ansible Engine, all versions 2.7.x, 2.8.x and 2.9.x prior to 2.7.17, 2.8.9 and 2.9.6     respectively, when using ansible_facts as a subkey of itself and promoting it to a variable when inject is     enabled, overwriting the ansible_facts after the clean. An attacker could take advantage of this by     altering the ansible_facts, such as ansible_hosts, users and any other key data which would lead into     privilege escalation or code injection. (CVE-2020-10684)

  - A flaw was found in Ansible Engine affecting Ansible Engine versions 2.7.x before 2.7.17 and 2.8.x before     2.8.11 and 2.9.x before 2.9.7 as well as Ansible Tower before and including versions 3.4.5 and 3.5.5 and     3.6.3 when using modules which decrypts vault files such as assemble, script, unarchive, win_copy, aws_s3     or copy modules. The temporary directory is created in /tmp leaves the s ts unencrypted. On Operating     Systems which /tmp is not a tmpfs but part of the root partition, the directory is only cleared on boot     and the decryp emains when the host is switched off. The system will be vulnerable when the system is not     running. So decrypted data must be cleared as soon as possible and the data which normally is encrypted     ble. (CVE-2020-10685)

  - A flaw was found in the use of insufficiently random values in Ansible. Two random password lookups of the     same length generate the equal value as the template caching action for the same file since no re-     evaluation happens. The highest threat from this vulnerability would be that all passwords are exposed at     once for the file. This flaw affects Ansible Engine versions before 2.9.6. (CVE-2020-10729)

  - 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 race condition flaw was found in Ansible Engine 2.7.17 and prior, 2.8.9 and prior, 2.9.6 and prior when     running a playbook with an unprivileged become user. When Ansible needs to run a module with become user,     the temporary directory is created in /var/tmp. This directory is created with umask 77 && mkdir -p     ; this operation does not fail if the directory already exists and is owned by another user. An     attacker could take advantage to gain control of the become user as the target directory can be retrieved     by iterating '/proc//cmdline'. (CVE-2020-1733)

  - A flaw was found in the Ansible Engine when the fetch module is used. An attacker could intercept the     module, inject a new path, and then choose a new destination path on the controller node. All versions in     2.7.x, 2.8.x and 2.9.x branches are believed to be vulnerable. (CVE-2020-1735)

  - A flaw was found in Ansible 2.7.16 and prior, 2.8.8 and prior, and 2.9.5 and prior when a password is set     with the argument password of svn module, it is used on svn command line, disclosing to other users     within the same node. An attacker could take advantage by reading the cmdline file from that particular     PID on the procfs. (CVE-2020-1739)

  - A flaw was found in Ansible Engine when using Ansible Vault for editing encrypted files. When a user     executes ansible-vault edit, another user on the same computer can read the old and new secret, as it is     created in a temporary file with mkstemp and the returned file descriptor is closed and the method     write_data is called to write the existing secret in the file. This method will delete the file before     recreating it insecurely. All versions in 2.7.x, 2.8.x and 2.9.x branches are believed to be vulnerable.
    (CVE-2020-1740)

  - A flaw was found in the Ansible Engine affecting Ansible Engine versions 2.7.x before 2.7.17 and 2.8.x     before 2.8.11 and 2.9.x before 2.9.7 as well as Ansible Tower before and including versions 3.4.5 and     3.5.5 and 3.6.3 when the ldap_attr and ldap_entry community modules are used. The issue discloses the LDAP     bind password to stdout or a log file if a playbook task is written using the bind_pw in the parameters     field. The highest threat from this vulnerability is data confidentiality. (CVE-2020-1746)

  - 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 flaw was found in the Ansible Engine 2.9.18, where sensitive info is not masked by default and is not     protected by the no_log feature when using the sub-option feature of the basic.py module. This flaw allows     an attacker to obtain sensitive information. The highest threat from this vulnerability is to     confidentiality. (CVE-2021-20228)

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.9.6 fixes the following issues :

Security issues fixed :

  - CVE-2019-14904: Fixed a vulnerability in solaris_zone     module via crafted solaris zone (boo#1157968).

  - CVE-2019-14905: Fixed an issue where malicious code     could craft filename in nxos_file_copy module     (boo#1157969).

  - CVE-2019-14864: Fixed Splunk and Sumologic callback     plugins leak sensitive data in logs (boo#1154830).

  - CVE-2019-14846: Fixed secrets disclosure on logs due to     display is hardcoded to DEBUG level (boo#1153452)

  - CVE-2019-14856: Fixed insufficient fix for     CVE-2019-10206 (boo#1154232)

  - CVE-2019-14858: Fixed data in the sub parameter fields     that will not be masked and will be displayed when run     with increased verbosity (boo#1154231) 

  - CVE-2019-10206: ansible-playbook -k and ansible cli     tools prompt passwords by expanding them from templates     as they could contain special characters. Passwords     should be wrapped to prevent templates trigger and     exposing them. (boo#1142690)

  - CVE-2019-10217: Fields managing sensitive data should be     set as such by no_log feature. Some of these fields in     GCP modules are not set properly.
    service_account_contents() which is common class for all     gcp modules is not setting no_log to True. Any sensitive     data managed by that function would be leak as an output     when running ansible playbooks. (boo#1144453)

An update of the ansible package has been released.

The version of Ansible Tower running on the remote web server is 3.5.x prior to 3.5.4 or 3.6.x prior to 3.6.2. It is, therefore, affected by multiple vulnerabilities.

  - An information disclosure vulnerability exists in the Sumologic and Splunk callback plugins due to Ansible     not respecting the 'no_log' flag. A remote attacker can exploit this via the plugin collectors to     potentially disclose sensitive information.  (CVE-2019-14864)

  - A flaw exists in RabbitMQ manager with the rabbitmq_enable_manager setting due to the setting exposing the     RabbigMQ manager management interface publicly, which may still have the default admin user active. An     unauthenticated, remote attacker can exploit this by guessing the default admin credentials and gain     access to the system. (CVE-2019-19340)

  - An information disclosure vulnerability exists in Ansible Tower backups, due to files in     '/var/backup/tower' being left world-readable while a Tower backup is running. An authenticated, remote     attacker with knowledge of the backup can exploit this by navigating to the '/var/backup/tower' directory     and accessing the files, which includes both the SECRET_KEY, backup files, and every credential stored in     Tower. (CVE-2019-19341)

  - An information disclosure vulnerability exists in '/websocket' due to Ansible Tower mishandling passwords     with the '#' character, and partially disclosing plaintext passwords when '/websocket' is requested. An     unauthenticated, remote attacker can exploit this via HTTP to disclose partial passwords, allowing the     attacker to brute force or guess predictable passwords. (CVE-2019-19342)

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 / 8 host has packages installed that are affected by a vulnerability as referenced in the RHSA-2019:3928 advisory.

  - Ansible: Splunk and Sumologic callback plugins leak sensitive data in logs (CVE-2019-14864)

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

An update for Ansible is now available for Ansible Engine 2.9.

Red Hat Product Security has rated this update as having a security impact of Moderate. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

Ansible is a simple model-driven configuration management, multi-node deployment, and remote-task execution system. Ansible works over SSH and does not require any software or daemons to be installed on remote nodes. Extension modules can be written in any language and are transferred to managed machines automatically.

Security Fix(es) :

Ansible: Splunk and Sumologic callback plugins leak sensitive data in logs (CVE-2019-14864)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The following packages have been upgraded to a newer upstream version:
ansible (2.9.1)

Bug Fix(es) :

See:
https://github.com/ansible/ansible/blob/v2.9.1/changelogs/CHANGELOG-v2 .9.rst for details on bug fixes in this release.

The remote Redhat Enterprise Linux 7 / 8 host has a package installed that is affected by a vulnerability as referenced in the RHSA-2019:3926 advisory.

  - Ansible: Splunk and Sumologic callback plugins leak sensitive data in logs (CVE-2019-14864)

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

The remote Redhat Enterprise Linux 7 host has a package installed that is affected by a vulnerability as referenced in the RHSA-2019:3925 advisory.

  - Ansible: Splunk and Sumologic callback plugins leak sensitive data in logs (CVE-2019-14864)

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

ID	Name	Product	Family	Severity
152270	Debian DSA-4950-1 : ansible - security update	Nessus	Debian Local Security Checks	high
135454	openSUSE Security Update : ansible (openSUSE-2020-513)	Nessus	SuSE Local Security Checks	high
133804	Photon OS 3.0: Ansible PHSA-2020-3.0-0058	Nessus	PhotonOS Local Security Checks	medium
133686	Photon OS 2.0: Ansible PHSA-2020-2.0-0207	Nessus	PhotonOS Local Security Checks	medium
132319	Ansible Tower 3.5.x < 3.5.4 / 3.6.x < 3.6.2 Multiple Vulnerabilities	Nessus	CGI abuses	high
131213	RHEL 7 / 8 : ansible (RHSA-2019:3928)	Nessus	Red Hat Local Security Checks	medium
131212	RHEL 7 / 8 : ansible (RHSA-2019:3927)	Nessus	Red Hat Local Security Checks	medium
131211	RHEL 7 / 8 : ansible (RHSA-2019:3926)	Nessus	Red Hat Local Security Checks	medium
131210	RHEL 7 : ansible (RHSA-2019:3925)	Nessus	Red Hat Local Security Checks	medium

Detections

Analytics

CVE-2019-14864

medium

Tenable Plugins

high

high

medium

medium

high

medium

medium

medium

medium