CVE-2018-10855

ansible: Failed tasks do not honour no_log option allowing for secrets to be disclosed in logs

Published Jul 2, 2018 CVSS 3.1 · 5.9 Medium EPSS 3.0% KEV · Not listed
Description
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.

Analysis

No analysis available yet

Remediation

No remediation available yet

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DSA Debian DSA DSA-4396-1 ansible security update
EUVD EUVD EUVD-2018-0015 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.
Github GHSA Github GHSA GHSA-jwcc-j78w-j73w Ansible exposes sensitive data in log files and on the terminal
Ubuntu USN Ubuntu USN USN-4072-1 Ansible vulnerabilities
History
Type Values Removed Values Added
Metrics epss

{'score': 0.02647}

epss

{'score': 0.02523}

Weaknesses
  • CWE-532

    Insertion of Sensitive Information into Log File

Sources

Status
PUBLISHED
Assigner
redhat
Published
Updated
Aug 5, 2024, 7:46 AM
Reserved
May 9, 2018, 12:00 AM
Status
Modified
Published
Jul 3, 2018, 1:29 AM
Modified
Jun 17, 2026, 1:34 AM
Severity
Moderate
Public date
Jun 11, 2018, 12:00 AM