High

Exposure of Sensitive Information to an Unauthorized Actor in ansible

  • Disclosed: 25.11.2019
  • Updated: 11.10.2026 11:20

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.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Python (PyPI) ansible >= 2.8.0a1, < 2.8.4 2.8.4

References

CVSS score 6.5/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Weakness (CWE)
CWE-200
Platform
Python (PyPI)
Package
ansible
Disclosed
25.11.2019
Updated
11.10.2026 11:20

Sources and licenses

OSV / GitHub Advisory Database - PYSEC-2019-3 - PyPA Advisory Database; CC BY 4.0

OSV / GitHub Advisory Database - GHSA-p75j-wc34-527c - CC BY 4.0

Vulnerability history: ansible

All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (68) in the archive
Total entries
68
First → latest
09.2013 12.2025
Without a fix
2
Exploited in attacks
0

Severity breakdown

  • Critical 9
  • High 24
  • Medium 27
  • Low 6
  • Unrated 2

Disclosures per year

  1. 2017: 3
  2. 2018: 12
  3. 2019: 8
  4. 2020: 29
  5. 2021: 7
  6. 2022: 3
  7. 2023: 1
  8. 2024: 0
  9. 2025: 1
  10. 2026: 0

earlier: 4

Severity:
  1. High · 7.5 CVE-2022-3697 >= 2.5.0, < 7.0.0 7.0.0
  2. High · 7.1 CVE-2021-3583 < 2.9.23rc1, >= 2.10.0a1, < 2.10.11rc1, >= 2.11.0a1, < 2.11.2rc1 2.9.23rc1, 2.10.11rc1, 2.11.2rc1
  3. High · 5.5 CVE-2021-20178 < 2.9.18 2.9.18
  4. High · 7.5 CVE-2021-20228 >= 2.10.0a1, < 2.10.6rc1, >= 2.9.0a1, < 2.9.18rc1, < 2.8.19rc1 2.10.6rc1, 2.9.18rc1, 2.8.19rc1
  5. High · 7.3 CVE-2019-14904 < 2.7.16, >= 2.8.0a1, < 2.8.8, >= 2.9.0a1, < 2.9.3 2.7.16, 2.8.8, 2.9.3
  6. High · 5.6 CVE-2019-14905 >= 2.7.0a1, < 2.7.16, >= 2.8.0a1, < 2.8.8, >= 2.9.0a1, < 2.9.3 2.7.16, 2.8.8, 2.9.3
  7. High · 7.8 CVE-2020-1737 >= 2.8.0a1, < 2.8.9, >= 2.9.0a1, < 2.9.6, < 2.7.17 2.8.9, 2.9.6, 2.7.17
  8. High · 7.4 CVE-2020-1734 >= 2.10.0a1, < 2.10.0rc1, >= 2.9.0a1, < 2.9.11, < 2.8.13 2.10.0rc1, 2.9.11, 2.8.13
  9. High · 6.5 CVE-2019-14856 >= 2.6.0, < 2.6.20, >= 2.7.0, < 2.7.14, >= 2.8.0, < 2.8.6 2.6.20, 2.7.14, 2.8.6
  10. Exposure of Sensitive Information to an Unauthorized Actor in ansible this entry
    High · 6.5 CVE-2019-10217 >= 2.8.0a1, < 2.8.4 2.8.4
  11. High · 7.5 CVE-2016-8614 < 2.2.0.0 2.2.0.0
Show more (13) Showing 20 of 33

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.