Upstream information

CVE-2018-10855 at MITRE

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.

SUSE information

Overall state of this security issue: Running

This issue is currently rated as having moderate severity.

CVSS v2 Scores
  National Vulnerability Database
Base Score 5
Vector AV:N/AC:L/Au:N/C:P/I:N/A:N
Access Vector Network
Access Complexity Low
Authentication None
Confidentiality Impact Partial
Integrity Impact None
Availability Impact None
CVSS v3 Scores
  SUSE
Base Score 5.9
Vector AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Access Vector Network
Access Complexity High
Privileges Required None
User Interaction None
Scope Unchanged
Confidentiality Impact High
Integrity Impact None
Availability Impact None
SUSE Bugzilla entries: 1097775 [IN_PROGRESS], 1099808 [IN_PROGRESS]

No SUSE Security Announcements cross referenced.

List of packages in QA

Product(s) Package(s)
HPE Helion Openstack 8
  • ansible >= 2.4.6.0-3.3.1
SUSE OpenStack Cloud 8
  • ansible >= 2.4.6.0-3.3.1
SUSE OpenStack Cloud Crowbar 8
  • ansible >= 2.4.6.0-3.3.1


Status of this issue by product and package

Please note that this evaluation state might be work in progress, incomplete or outdated. Also information for service packs in the LTSS phase is only included for issues meeting the LTSS criteria. If in doubt, feel free to contact us for clarification.

Product(s) Source package State
HPE Helion OpenStack 8 ansible In progress
SUSE Openstack Cloud 7 ansible Not affected
SUSE Openstack Cloud 8 ansible In progress