Skip to content
Fencer Intel
medium 5.7

CVE-2019-10217 json

Exposure of Sensitive Information to an Unauthorized Actor in ansible

published 6y ago modified 4mo ago also GHSA-p75j-wc34-527c , PYSEC-2019-3 , EUVD-2019-0007

cvss
5.7
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.9%
EPSS 1.9% chance of exploitation in 30 days, percentile 79%
public exploits
0
none known

Summary

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.

Patch / fix

  • pypi ansible 2.8.4
  • redhat ansible 2.8.4
  • ansible Debian 14, Debian 13, Debian 12 2.8.6+dfsg-1

debian advisories DEBIAN-CVE-2019-10217

  • ansible ansible engine 2.8, ansible engine 2 2.8.4-1.el7ae
  • ansible ansible engine 2.8, ansible engine 2 2.8.4-1.el8ae

red hat advisories RHSA-2019:2543RHSA-2019:2542

  • storm OpenStack Cloud Crowbar 8, OpenStack Cloud 8, HPE Helion OpenStack 8 1.2.3-3.6.1
  • ansible OpenStack Cloud Crowbar 8, OpenStack Cloud 8, HPE Helion OpenStack 8 2.9.14-3.15.1
  • grafana OpenStack Cloud Crowbar 8, OpenStack Cloud 8, HPE Helion OpenStack 8 6.7.4-4.12.1
  • ardana-mq OpenStack Cloud 8, HPE Helion OpenStack 8 8.0+git.1593618123.678c32b-3.26.1
  • ardana-nova OpenStack Cloud 8, HPE Helion OpenStack 8 8.0+git.1601298847.dd01585-3.42.1
  • crowbar-core OpenStack Cloud Crowbar 8 5.0+git.1600432272.b3ad722f0-3.44.1
  • python-kombu OpenStack Cloud Crowbar 8, OpenStack Cloud 8, HPE Helion OpenStack 8 4.1.0-3.7.1
  • ardana-cinder OpenStack Cloud 8, HPE Helion OpenStack 8 8.0+git.1596129856.263f430-3.43.1

suse advisories SUSE-SU-2020:3309-1

  • ansible-14 openSUSE Tumbleweed 14.6.0-1.1
  • ansible-13 openSUSE Tumbleweed 13.7.0-1.1
  • ansible-12 openSUSE Tumbleweed 12.2.0-1.1
  • ansible-11 openSUSE Tumbleweed 11.11.0-1.1
  • ansible-10 openSUSE Tumbleweed 10.6.0-1.1
  • ansible-9 openSUSE Tumbleweed 9.8.0-1.1
  • ansible Package Hub 15 SP1 2.9.6-bp151.3.6.1
  • ansible openSUSE Leap 15.1 2.9.6-lp151.2.7.1

opensuse advisories openSUSE-SU-2026:12447-1openSUSE-SU-2026:10944-1openSUSE-SU-2025:15753-1openSUSE-SU-2025:15605-1openSUSE-SU-2024:14536-1openSUSE-SU-2024:14244-1

  • ansible Alpine 3.12, Alpine 3.11, Alpine 3.10 2.8.4-r0
  • ansible-base Alpine 3.15, Alpine 3.14, Alpine 3.13 2.8.4-r0

alpine advisories ALPINE-CVE-2019-10217

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2019-10217 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-10217 updated cvss 5.7

Ansible: gcp modules do not flag sensitive data fields properly

  • Red Hat Ansible Engine 2 for RHEL 7 ansible 2.8.4-1.el7ae Red Hat Ansible Engine 2 for RHEL 8 ansible 2.8.4-1.el8ae
    fixed: vendor fix RHSA-2019:2543
  • Red Hat Ansible Engine 2.8 for RHEL 7 Server ansible 2.8.4-1.el7ae Red Hat Ansible Engine 2.8 for RHEL 8 ansible 2.8.4-1.el8ae
    fixed: vendor fix RHSA-2019:2542
  • Red Hat Ceph Storage 2 ansible Red Hat Ceph Storage 3 ansible Red Hat OpenStack Platform 10 (Newton) ansible Red Hat OpenStack Platform 13 (Queens) ansible Red Hat OpenStack Platform 14 (Rocky) ansible
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.85% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/ansible/ansible/issues/56269 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.0 5.7 CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
pypi ansible
>=2.8.0a1, <2.8.4
>=2.8.0, <2.8.4
2.8.4

Affected products

  • Red Hat Ansible

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.