Skip to content
OpenAdvisories
High SUSE-SU-2018:4130-1 3 CVEs

Security update for ansible

Published Dec 14, 2018 · Updated Feb 4, 2026

Summary

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)

Fixed packages 3

ReleasePackageFixed in
SUSE · HPE Helion OpenStack 8 ansible 2.4.6.0-3.3.1
SUSE · OpenStack Cloud 8 ansible 2.4.6.0-3.3.1
SUSE · OpenStack Cloud Crowbar 8 ansible 2.4.6.0-3.3.1

Vulnerabilities 3

  • High 7.8

    Ansible Improper Input Validation vulnerability

    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.

  • High 7.8

    Ansible Arbitrary Code Execution

    A flaw was found in ansible. 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.

  • Medium 5.9

    Ansible exposes sensitive data in log files and on the terminal

    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 expo…

References

  • report
    https://bugzilla.suse.com/1097775
  • report
    https://bugzilla.suse.com/1099805
  • report
    https://bugzilla.suse.com/1099808
  • web
    https://www.suse.com/security/cve/CVE-2018-10855
  • web
    https://www.suse.com/security/cve/CVE-2018-10874
  • web
    https://www.suse.com/security/cve/CVE-2018-10875