CVE-2018-10855

unknown

Published 2018-10-10 · Modified 2023-11-08

💬 Discuss on Community ✚ Propose mitigation

CVSS v3

—

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

CVSS v4 NEW

—

not yet in upstream

VIR risk

—

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.

Predictions

Exploit likelihood

30%

Patch ETA

—

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.

✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

OS impact

SUSE Affected 1 release

Version	Status	Fixed in
—	Affected	—

Debian Fixed 5 releases

Version	Status	Fixed in
trixie	Fixed	`2.5.5+dfsg-1`
sid	Fixed	`2.5.5+dfsg-1`
forky	Fixed	`2.5.5+dfsg-1`
bullseye	Fixed	`2.5.5+dfsg-1`
bookworm	Fixed	`2.5.5+dfsg-1`

Package impact

Ecosystem	Package	Vulnerable	Fixed
PyPI	ansible	`>=2.5.0a1,<2.5.5`	`2.5.5`
PyPI	ansible	`>=2.4.0.0,<2.4.5.0`	`2.4.5.0`
PyPI	ansible	`>=2.4,<2.4.5.0`	`2.5.5`

References

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.