Skip to content
Fencer Intel
medium 5.0

CVE-2020-1753 json

Insertion of Sensitive Information into Log File, Invocation of Process Using Visible Sensitive Information, and Exposure of Sensitive Information to an Unauthorized Actor in Ansible

published 6y ago modified 4mo ago also GHSA-86hp-cj9j-33vv , PYSEC-2020-210 , EUVD-2020-0022

cvss
5.0
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 43%
public exploits
0
none known

Summary

A security flaw was found in Ansible Engine, all Ansible 2.7.x versions prior to 2.7.17, all Ansible 2.8.x versions prior to 2.8.11 and all Ansible 2.9.x versions prior to 2.9.7, when managing kubernetes using the k8s module. Sensitive parameters such as passwords and tokens are passed to kubectl from the command line, not using an environment variable or an input configuration file. This will disclose passwords and tokens from process list and no_log directive from debug module would not have any effect making these secrets being disclosed on stdout and log files.

Patch / fix

  • pypi ansible 2.7.18, 2.8.11, 2.8.12, 2.9.7
  • redhat ansible_engine 2.7.18, 2.8.11, 2.9.7
  • ansible Debian 14, Debian 13, Debian 12 2.9.16+dfsg-1

debian advisories DEBIAN-CVE-2020-1753

  • ansible ansible engine 2.9, ansible engine 2 2.9.7-1.el7ae
  • ansible ansible engine 2.9, ansible engine 2 2.9.7-1.el8ae
  • ansible-test ansible engine 2.9, ansible engine 2 2.9.7-1.el7ae
  • ansible-test ansible engine 2.9, ansible engine 2 2.9.7-1.el8ae
  • ansible ansible engine 2.7 2.7.18-1.el7ae
  • ansible ansible engine 2.8 2.8.16-1.el7ae
  • ansible ansible engine 2.8 2.8.16-1.el8ae

red hat advisories RHSA-2020:1542RHSA-2020:1541RHSA-2020:2142RHBA-2020:4195

  • ansible openSUSE Leap 15.5, Manager Proxy Module 4.3, Manager Client Tools 15 2.9.27-150000.1.17.2
  • grafana Manager Client Tools 15 9.5.18-150000.1.63.2
  • spacecmd openSUSE Leap 15.5, Manager Client Tools 15 4.3.27-150000.3.116.2
  • mgr-daemon Manager Client Tools 15 4.3.9-150000.1.47.2
  • spacewalk-koan Manager Client Tools 15 4.3.6-150000.3.33.2
  • dracut-saltboot openSUSE Leap 15.5, Manager Client Tools for SLE Micro 5, Manager Client Tools 15 0.1.1710765237.46af599-150000.1.53.2
  • POS_Image-JeOS7 openSUSE Leap 15.5, Manager Client Tools 15 0.1.1710765237.46af599-150000.1.21.2
  • uyuni-common-libs Manager Client Tools 15 4.3.10-150000.1.39.2

suse advisories SUSE-SU-2024:1509-1SUSE-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 SP3, openSUSE Leap 15.3 2.9.21-bp153.2.3.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

Is CVE-2020-1753 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-2020-1753 updated cvss 5.0

Ansible: kubectl connection plugin leaks sensitive information

  • Red Hat OpenStack Platform 10 (Newton) ansible Red Hat OpenStack Platform 13 (Queens) ansible
    affected: workaround, no fix planned “Currently, there is no mitigation for this issue.”
  • Red Hat Ansible Engine 2 for RHEL 7 ansible 2.9.7-1.el7ae, ansible-test 2.9.7-1.el7ae Red Hat Ansible Engine 2 for RHEL 8 ansible 2.9.7-1.el8ae, ansible-test 2.9.7-1.el8ae
    fixed: vendor fix “Currently, there is no mitigation for this issue.” RHSA-2020:1542
  • Red Hat Ansible Engine 2.7 for RHEL 7 Server ansible 2.7.18-1.el7ae
    fixed: vendor fix “Currently, there is no mitigation for this issue.” RHSA-2020:2142
  • Red Hat Ansible Engine 2.8 for RHEL 7 Server ansible 2.8.16-1.el7ae Red Hat Ansible Engine 2.8 for RHEL 8 ansible 2.8.16-1.el8ae
    fixed: vendor fix “Currently, there is no mitigation for this issue.” RHBA-2020:4195
  • Red Hat Ansible Engine 2.9 for RHEL 7 Server ansible 2.9.7-1.el7ae, ansible-test 2.9.7-1.el7ae Red Hat Ansible Engine 2.9 for RHEL 8 ansible 2.9.7-1.el8ae, ansible-test 2.9.7-1.el8ae
    fixed: vendor fix “Currently, there is no mitigation for this issue.” RHSA-2020:1541
  • Red Hat Ansible Tower 3.4 for RHEL 7 Server ansible-tower-34/ansible-tower-memcached 1.4.15-28, ansible-tower-35/ansible-tower-memcached 1.4.15-28, ansible-tower-37/ansible-tower-memcached-rhel7 1.4.15-28
    fixed: vendor fix “Currently, there is no mitigation for this issue.” RHBA-2020:0547
  • Red Hat Ansible Tower 3.5 for RHEL 7 Server ansible-tower-35/ansible-tower 3.5.6-1
    fixed: vendor fix “Currently, there is no mitigation for this issue.” RHBA-2020:1539
  • Red Hat Ceph Storage 2 ansible Red Hat Ceph Storage 3 ansible Red Hat Storage 3 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

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

Exploits and checks

  • github.com https://github.com/ansible-collections/kubernetes/pull/51 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Affected packages

ecosystem package affected fixed in
pypi ansible
>=2.7.0a1, <2.7.18
>=2.8.0a1, <2.8.12
>=2.9.0a1, <2.9.7
<2.7.18
>=2.8.0, <2.8.11
>=2.9.0, <2.9.7
2.7.18
2.8.12
2.9.7
2.8.11

Affected products

  • Red Hat Ansible

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
  • CWE-214 Invocation of Process Using Visible Sensitive Information
  • CWE-532 Insertion of Sensitive Information into Log File

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.