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 expose sensitive data in log files and on the terminal of the user running Ansible.
01
beschreibt (1)
Zugehörige CVEs.
| ID | Schweregrad | ausnutzbar | ||
|---|---|---|---|---|
| CVE-2018-10855US | medium5.9 | — | ||
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 tas… | ||||
02
Referenzen
Externe Belege — Patches, Meldungen, Analysen.
- https://access.redhat.com/errata/RHBA-2018:3788ADVISORY
- https://access.redhat.com/errata/RHSA-2018:1948ADVISORY
- https://access.redhat.com/errata/RHSA-2018:1949ADVISORY
- https://access.redhat.com/errata/RHSA-2018:2022ADVISORY
- https://access.redhat.com/errata/RHSA-2018:2079ADVISORY
- https://access.redhat.com/errata/RHSA-2018:2184ADVISORY
- https://access.redhat.com/errata/RHSA-2018:2585ADVISORY
- https://access.redhat.com/errata/RHSA-2019:0054ADVISORY
scry
Advisories wie diese benennen die exponierten Produkte, die Angreifer auf Ihrer Angriffsfläche ins Visier nehmen. Sehen Sie mit einem kostenlosen Passiv-Scan, was exponiert ist.
Kostenloser Scan