CVE-2017-7481

Ansible before versions 2.1.6.0, 2.2.3.0, 2.3.1.0, and 2.4.0.0 fails to properly mark lookup-plugin results as unsafe. If an attacker could control the results of lookup() calls, they could inject Unicode strings to be parsed by the jinja2 templating system, resulting in code execution. By default, the jinja2 templating language is now marked as 'unsafe' and is not evaluated.

Ansible before versions 2.3.1.0 and 2.4.0.0 fails to properly mark lookup-plugin results as unsafe. If an attacker could control the results of lookup() calls, they could inject Unicode strings to be parsed by the jinja2 templating system, resulting in code execution. By default, the jinja2 templating language is now marked as 'unsafe' and is not evaluated.

It was found that 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).

It is reported that in Ansible, under some circumstances the mysql_user module may fail to correctly change a password. Thus an old password may still be active when it should have been changed (CVE-2016-8647).

Data for lookup plugins used as variables was not being correctly marked as "unsafe" (CVE-2017-7481).

The ansible package has been updated to version 2.3.1 to fix these issues and several other bugs.

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.

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.

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 before versions 2.3.1.0 and 2.4.0.0 fails to properly mark lookup-plugin results as unsafe. If an attacker could control the results of lookup() calls, they could inject Unicode strings to be parsed by the jinja2 templating system, resulting in code execution. By default, the jinja2 templating language is now marked as 'unsafe' and is not evaluated.

This update for ansible provides version 2.2.3.0 and fixes the following security issues:

• CVE-2017-7481: Data for lookup plugins used as variables was not being marked as 'unsafe' and could lead to unintentional disclosure of information. (bsc#1038785)
• CVE-2016-9587: Prevent compromised host to execute commands on the controller (bsc#1019021).
• CVE-2017-7466: Prevent arbitrary code execution on control nodes.

For more information about the upstream bugs fixed, please see /usr/share/doc/packages/ansible/CHANGELOG.md

Additionally, monasca-installer received several compatibility fixes for ansible.

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)