VDB

CVE-2018-10855

CVE-2018-10855 PUBLISHED CVSS 5.9 MEDIUM

Ansible exposes sensitive data in log files and on the terminal

Reported by redhat · Published July 2, 2018

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.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
ansibleUbuntu:18.04:LTS2.5.1+dfsg-1ubuntu0.1

Risk scores

CVSS 3.0
5.9
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected products

VendorProductVersions
[UNKNOWN]ansibleAnsible 2.4.5, Ansible 2.5.5
[UNKNOWN]ansible2.4.5, 2.5.5
PyPIansible2.5.0a1, 2.4.0.0
alpineansible0

Timeline

  • Jun 19, 2018 CVE Published
  • Apr 14, 2021 EPSS Score (30 in total, the first dated here)
  • Nov 21, 2024 CVE Updated
  • Mar 6, 2026 Distribution Patch (9 in total, the first dated here)
  • Mar 6, 2026 Security Advisory (14 in total, the first dated here)
  • Sep 26, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2018-10855
vulnetix vdb fixes CVE-2018-10855

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2018-10855/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›