CVE-2018-10855

Ansible 2.5 prior to 2.5.5, and 2.4 prior to 2.4.5, do not honor the no_log task flag for failed tasks. When the no_log flag has been used to protect sensitive data passed to a task from being logged, and that task does not run successfully, Ansible will expose sensitive data in log files and on the terminal of the user running Ansible.

Ansible 2.5 prior to 2.5.5, and 2.4 prior to 2.4.5, do not honor the no_log task flag for failed tasks. When the no_log flag has been used to protect sensitive data passed to a task from being logged, and that task does not run successfully, Ansible will expose sensitive data in log files and on the terminal of the user running Ansible.

Ansible 2.5 prior to 2.5.5, and 2.4 prior to 2.4.5, do not honor the no_log task flag for failed tasks. When the no_log flag has been used to protect sensitive data passed to a task from being logged, and that task does not run successfully, Ansible will expose sensitive data in log files and on the terminal of the user running Ansible.

Ansible prior to 2.4.5 does not honor the no_log task flag for failed tasks. When the no_log flag has been used to protect sensitive data passed to a task from being logged, and that task does not run successfully, Ansible will expose sensitive data in log files and on the terminal of the user running Ansible (CVE-2018-10855).

This update for ansible fixes the following issues:

Security vulnerabilities fixed:

• CVE-2018-16876: Respect no_log on retry and high verbosity (bsc#1118896)
• CVE-2018-16859: Windows - prevent sensitive content from appearing in scriptblock logging (bsc#1116587)
• CVE-2018-10855: Fixed the honouration of the no_log option with failed task iterations (boo#1097775)
• CVE-2017-7466: Fixed an input validation vulnerability in Ansible's handling of data sent from client systems
• CVE-2017-7481: Fixed a security issue with lookup return not tainting the jinja2 environment (bsc#1038785)

Other bug fixes and changes:

• Update to version 2.7.6
  • Added log message at -vvvv when using netconf connection listing connection details.
  • Changes how ansible-connection names socket lock files. They now use the same name as the socket itself, and as such do not lock other attempts on connections to the same host, or cause issues with overly-long hostnames.
  • Fix mandatory statement error for junos modules (https://github.com/ansible/ansible/pull/50138)
  • Moved error in netconf connection plugin from at import to on connection.
  • This reverts some changes from commit 723daf3. If a line is found in the file, exactly or via regexp matching, it must not be added again. insertafter/insertbefore options are used only when a line is to be inserted, to specify where it must be added.
  • allow using openstack inventory plugin w/o a cache
  • callbacks - Do not filter out exception, warnings, deprecations on failure when using debug (https://github.com/ansible/ansible/issues/47576)
  • certificate_complete_chain - fix behavior when invalid file is parsed while reading intermediate or root certificates.
  • copy - Ensure that the src file contents is converted to unicode in diff information so that it is properly wrapped by AnsibleUnsafeText to prevent unexpected templating of diff data in Python3 (https://github.com/ansible/ansible/issues/45717)
  • correct behaviour of verify_file for vmware inventory plugin, it was always returning True
  • dnf - fix issue where conf_file was not being loaded properly
  • dnf - fix update_cache combined with install operation to not cause dnf transaction failure
  • docker_container - fix network_mode idempotency if the container:<container-name> form is used (as opposed to container:<container-id>) (https://github.com/ansible/ansible/issues/49794)
  • docker_container - warning when non-string env values are found, avoiding YAML parsing issues. Will be made an error in Ansible 2.8. (https://github.com/ansible/ansible/issues/49802)
  • docker_swarm_service - Document labels and container_labels with correct type.
  • docker_swarm_service - Document limit_memory and reserve_memory correctly on how to specify sizes.
  • docker_swarm_service - Document minimal API version for configs and secrets.
  • docker_swarm_service - fix use of Docker API so that services are not detected as present if there is an existing service whose name is a substring of the desired service
  • docker_swarm_service - fixing falsely reporting update_order as changed when option is not used.
  • document old option that was initally missed
  • ec2_instance now respects check mode https://github.com/ansible/ansible/pull/46774
  • fix for network_cli - ansible_command_timeout not working as expected (#49466)
  • fix handling of firewalld port if protocol is missing
  • fix lastpass lookup failure on python 3 (https://github.com/ansible/ansible/issues/42062)
  • flatpak - Fixed Python 2/3 compatibility
  • flatpak - Fixed issue where newer versions of flatpak failed on flatpak removal
  • flatpak_remote - Fixed Python 2/3 compatibility
  • gcp_compute_instance - fix crash when the instance metadata is not set
  • grafana_dashboard - Fix a pair of unicode string handling issues with version checking (https://github.com/ansible/ansible/pull/49194)
  • host execution order - Fix reverse_inventory not to change the order of the…

These are all security issues fixed in the ansible-2.9.24-1.2 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the ansible-9-9.8.0-1.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the ansible-10-10.6.0-1.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the ansible-11-11.11.0-1.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the ansible-12-12.2.0-1.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the ansible-13-13.7.0-1.1 package on the GA media of openSUSE Tumbleweed.

Ansible 2.5 prior to 2.5.5, and 2.4 prior to 2.4.5, do not honor the no_log task flag for failed tasks. When the no_log flag has been used to protect sensitive data passed to a task from being logged, and that task does not run successfully, Ansible will expose sensitive data in log files and on the terminal of the user running Ansible.

This update for ansible fixes the following issues:

Ansible was updated to ansible 2.4.6.0.

The full release notes can be found on:

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

Security issues fixed:

• CVE-2018-10875: ansible.cfg is read from the current working directory which can be altered to make it point to a plugin or a module path under the control of an attacker, thus allowing the attacker to execute arbitrary code. (bsc#1099808)
• CVE-2018-10874: 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. (bsc#1099805)
• CVE-2018-10855: Ansible did not honor the no_log task flag for failed tasks. When the no_log flag has been used to protect sensitive data passed to a task from being logged, and that task does not run successfully, Ansible will expose sensitive data in log files and on the terminal of the user running Ansible. (bsc#1097775)

It was discovered that Ansible failed to properly handle sensitive information. A local attacker could use those vulnerabilities to extract them. (CVE-2017-7481) (CVE-2018-10855) (CVE-2018-16837) (CVE-2018-16876) (CVE-2019-10156)

It was discovered that Ansible could load configuration files from the current working directory containing crafted commands. An attacker could run arbitrary code as result. (CVE-2018-10874) (CVE-2018-10875)

It was discovered that Ansible fetch module had a path traversal vulnerability. A local attacker could copy and overwrite files outside of the specified destination. (CVE-2019-3828)