CVE-2018-10855: Ansible exposes sensitive data in log files and on the terminal

CVE-2018-10855 · Severity: low · CVSS 3.1 · Published 2018-07-03

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.

Technologies: ansible (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2018-10855 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2018-10855 being exploited in the wild.
How severe is CVE-2018-10855?
Low severity, with a CVSS score of 3.1, published 3 July 2018.
Which products and versions are affected?
ansible (PyPI) ECOSYSTEM:introduced=2.5,fixed=2.5.5,introduced=2.4,fixed=2.4.5.0, ECOSYSTEM:introduced=2.5.0a1,fixed=2.5.5.
Is there a fix for CVE-2018-10855?
Yes. ansible (PyPI): upgrade to 2.4.5.0, 2.5.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2018-10855?
Check whether you run ansible (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • ansible (PyPI): upgrade to 2.4.5.0, 2.5.5 or later
    pip install "ansible>=2.5.5"

Affected products

  • ansible (PyPI) ECOSYSTEM:introduced=2.5,fixed=2.5.5,introduced=2.4,fixed=2.4.5.0, ECOSYSTEM:introduced=2.5.0a1,fixed=2.5.5

Identifiers

  • CVE-2018-10855
  • GHSA-jwcc-j78w-j73w
  • PYSEC-2018-42

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.