ansible-core sensitive data exposure in warning and deprecation output
Red Hat ansible-core
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat ansible-core |
| No fix yet |
Original description
A flaw was found in ansible-core. When a task or its parameters are marked no_log: true, sensitive values passed to a module's warn() or deprecate() calls are not redacted and are printed in cleartext to stdout/stderr in warning and deprecation messages. The 'warnings' and 'deprecations' keys are retained in the PRESERVE allow-list in lib/ansible/_internal/_task.py when the task result is censored, so sensitive parameters bypass masking and can be disclosed in output captured in terminal sessions, CI logs, and any automation wrapping ansible-playbook, even though every task touching the secrets is marked no_log: true.
From the CVE record · redhat