ZDF
Sign inSign up

Vulnerabilities

Security incident · CVE-2019-10217

A flaw was found in ansible 2.8.0 before 2.8.4.

Published Nov 25, 2019 · catalog updated Jun 17, 2026 · A flaw was found

Last checked Nov 6, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2019-10217. EPSS is 1.85%. Act only if a listed version of A flaw was found is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (A flaw was found).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
Medium6.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
1.85%
Remediation
Version ranges on file
Affected products
cpe redhat/ansible

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe redhat/ansible< 2.8.4

How to fix CVE-2019-10217

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2019-10217. EPSS is 1.85%. Act only if a listed version of A flaw was found is installed.

Which versions are affected?

Compare what you have installed with < 2.8.4. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-200: Exposure of Sensitive Information. EPSS 1.85%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Ansible security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Nov 25, 2019 · Monitored products — high

    Detected

    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.

  2. Jun 17, 2026 · Monitored products — high

    Updated

    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.

Sources

  • CVE.orgVulnerability recordCVE-2019-10217

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2019-10217

    30-day exploitation probability 1.85%

    first.org
  • Monitored products — highVendor advisoryCVE-2019-10217

    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.

    nvd.nist.gov

References

Freshness

Last verified in this catalog Nov 6, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • FIRST EPSSNov 6, 2026
  • CVE.orgNov 4, 2026
  • Monitored products — highNov 2, 2026