First published: Thu Oct 10 2019(Updated: )
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` options in the sub parameters are processed. As a result, data in the sub parameter fields will not be masked and will be displayed if Ansible is run with increased verbosity and present in the module invocation arguments for the task.
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/ansible-engine | <2.6.20 | 2.6.20 |
redhat/ansible-engine | <2.7.14 | 2.7.14 |
redhat/ansible-engine | <2.8.6 | 2.8.6 |
pip/ansible | >=2.0<2.6.20 | 2.6.20 |
pip/ansible | >=2.7.0a1<2.7.14 | 2.7.14 |
pip/ansible | >=2.8.0a1<2.8.6 | 2.8.6 |
pip/ansible | >=2.9.0a1<2.9.0rc4 | 2.9.0rc4 |
Red Hat Ansible Engine | >=2.0<=2.8.0 | |
Red Hat Ansible Tower | >=3.0<=3.5.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-14858 has a moderate severity rating due to its potential impact on the confidentiality of sensitive data.
To fix CVE-2019-14858, update Ansible to version 2.9.0 or later if you are using Ansible Engine, or Ansible Tower to 3.6 or later.
CVE-2019-14858 affects Ansible Engine versions 2.x up to 2.8 and Ansible Tower versions 3.x up to 3.5.
The potential risks of CVE-2019-14858 include unauthorized data disclosure due to improper handling of module arguments.
The best workaround for CVE-2019-14858 is to avoid using invalid parameter names in module arguments until a patch is applied.