Ansible leaks sensitive information to logs when told not to
Red Hat Ansible
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| ansible PyPI |
|
|
Red Hat Ansible
| Product | Affected | Fixed in |
|---|---|---|
| ansible PyPI |
|
|
2.6.202.8.1A 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.
From the CVE record · redhat
Ansible engine 2.x up to 2.8 and Ansible Tower 3.x up to 3.5 may expose values from subparameters marked no_log when a module receives an invalid parameter name. The task fails before those values are masked, so they can appear when Ansible runs with increased verbosity and the values are present in the task's module invocation arguments. The input does not specify network access, authentication, or user-interaction requirements.
Teams running Ansible engine 2.x up to 2.8, Ansible Tower 3.x up to 3.5, or the affected PyPI ansible package versions should check their deployments.