Summary
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)
This update was imported from the openSUSE:Leap:15.1:Update update project.
Fixed packages 1
| Release | Package | Fixed in |
|---|---|---|
| SUSE · Package Hub 15 SP1 | ansible | 2.9.6-bp151.3.6.1 |
Vulnerabilities 8
-
High 7.3
Ansible Uses Plugins That Disclose Credentials
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. …
-
High 7.3
Ansible leaks sensitive information to logs when told not to
A vulnerability was found in Ansible engine 2.x up to 2.8 and Ansible tower 3.x up to 3.5. When a module has an argument_spec with sub parameters marked as no_log, passing an invalid parameter name to the module will cause the task to fail before the no_log o…
-
High 7.3
OS Command Injection and Improper Input Validation in ansible
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 ad…
-
High 7.3
Externally Controlled Reference to a Resource in Another Sphere, Improper Input Validation, and External Control of File Name or Path in Ansible
A vulnerability was found in Ansible Engine versions 2.9.x before 2.9.3, 2.8.x before 2.8.8, 2.7.x before 2.7.16 and earlier, where in Ansible's nxos_file_copy module can be used to copy files to a flash or bootflash on NXOS devices. Malicious code could craf…
-
Medium 6.4
Ansible password prompts could expose passwords
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…
-
Medium 6.4
Ansible password prompts could expose passwords
ansible before versions 2.8.6, 2.7.14, 2.6.20 is vulnerable to a None
-
Medium 5.7
Exposure of Sensitive Information to an Unauthorized Actor in ansible
A flaw was found in ansible 2.8.0 before 2.8.4. 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 setti…
-
Medium 5.7
Inclusion of Sensitive Information in Log Files and Improper Output Neutralization for Logs in Ansible
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 disclos…
References
-
report
https://bugzilla.suse.com/1137479
-
report
https://bugzilla.suse.com/1142542
-
report
https://bugzilla.suse.com/1142690
-
report
https://bugzilla.suse.com/1144453
-
report
https://bugzilla.suse.com/1153452
-
report
https://bugzilla.suse.com/1154231
-
report
https://bugzilla.suse.com/1154232
-
report
https://bugzilla.suse.com/1154830
-
report
https://bugzilla.suse.com/1157968
-
report
https://bugzilla.suse.com/1157969
-
web
https://www.suse.com/security/cve/CVE-2019-10206
-
web
https://www.suse.com/security/cve/CVE-2019-10217
-
web
https://www.suse.com/security/cve/CVE-2019-14846
-
web
https://www.suse.com/security/cve/CVE-2019-14856
-
web
https://www.suse.com/security/cve/CVE-2019-14858
-
web
https://www.suse.com/security/cve/CVE-2019-14864
-
web
https://www.suse.com/security/cve/CVE-2019-14904
-
web
https://www.suse.com/security/cve/CVE-2019-14905