Information Exposure Affecting ansible package, versions <0:2.8.4-1.el7ae


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.26% (67th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL7-ANSIBLE-3374444
  • published26 Mar 2023
  • disclosed26 Jul 2019

Introduced: 26 Jul 2019

CVE-2019-10217  (opens in a new tab)
CWE-200  (opens in a new tab)

How to fix?

Upgrade RHEL:7 ansible to version 0:2.8.4-1.el7ae or higher.
This issue was patched in RHSA-2019:2542.

NVD Description

Note: Versions mentioned in the description apply only to the upstream ansible package and not the ansible package as distributed by RHEL. See How to fix? for RHEL:7 relevant fixed versions and status.

A flaw was found in ansible 2.8.0 before 2.8.4. Fields managing sensitive data should be set as such by no_log feature. Some of these fields in GCP modules are not set properly. service_account_contents() which is common class for all gcp modules is not setting no_log to True. Any sensitive data managed by that function would be leak as an output when running ansible playbooks.

CVSS Scores

version 3.1