CVE-2020-1753: Infoleak

Published Mar 6, 2020
·
Updated

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 nolog directive from debug module would not have any effect making these secrets being disclosed on stdout and log files.

Other sources

When the user configures 'kubectl' Ansible connection plugin to connect to Kubernetes and uses environment variables such as 'K8SAUTHPASSWORD' and 'K8SAUTHTOKEN' are revealed in stdout with verbose mode, logs and visible through process list.

Red Hat

Affected Software

18 affected componentsFixes available
debian/ansible
2.7.7+dfsg-1+deb10u12.7.7+dfsg-1+deb10u22.10.7+merged+base+2.10.8+dfsg-17.3.0+dfsg-17.7.0+dfsg-3
redhat/ansible-engine<2.7.18
2.7.18
redhat/ansible-engine<2.8.11
2.8.11
redhat/ansible-engine<2.9.7
2.9.7
pip/ansible>=2.9.0a1<2.9.7
2.9.7
pip/ansible>=2.8.0a1<2.8.12
2.8.12
pip/ansible>=2.7.0a1<2.7.18
2.7.18
redhat Ansible Engine<2.7.18
redhat Ansible Engine>=2.8.0<2.8.11
redhat Ansible Engine>=2.9.0<2.9.7
redhat Ansible Tower<=3.3.4
redhat Ansible Tower>=3.4.0<=3.4.5
redhat Ansible Tower>=3.5.0<=3.5.5
redhat Ansible Tower>=3.6.0<=3.6.3
Debian Debian Linux=10.0
Fedoraproject Fedora=30
Fedoraproject Fedora=31
Fedoraproject Fedora=32

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/ansible to a version that resolves this vulnerability.

    Fixed in 2.7.7+dfsg-1+deb10u1Fixed in 2.7.7+dfsg-1+deb10u2Fixed in 2.10.7+merged+base+2.10.8+dfsg-1Fixed in 7.3.0+dfsg-1Fixed in 7.7.0+dfsg-3
  2. Upgrade

    Upgrade redhat/ansible-engine to a version that resolves this vulnerability.

    Fixed in 2.7.18
  3. Upgrade

    Upgrade redhat/ansible-engine to a version that resolves this vulnerability.

    Fixed in 2.8.11
  4. Upgrade

    Upgrade redhat/ansible-engine to a version that resolves this vulnerability.

    Fixed in 2.9.7
  5. Upgrade

    Upgrade pip/ansible to a version that resolves this vulnerability.

    Fixed in 2.9.7
  6. Upgrade

    Upgrade pip/ansible to a version that resolves this vulnerability.

    Fixed in 2.8.12
  7. Upgrade

    Upgrade pip/ansible to a version that resolves this vulnerability.

    Fixed in 2.7.18
  8. Upgrade

    Upgrade Ansible Engine to a version that resolves this vulnerability.

    Fixed in 2.7.17
  9. Upgrade

    Upgrade Ansible Engine to a version that resolves this vulnerability.

    Fixed in 2.8.11
  10. Upgrade

    Upgrade Ansible Engine to a version that resolves this vulnerability.

    Fixed in 2.9.7

Event History

Mar 16, 2020
CVE Published
via MITRE·02:37 PM
Data Sourced
via MITRE·02:37 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Apr 7, 2021
Advisory Published
via GitHub·08:33 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is CVE-2020-1753?

CVE-2020-1753 is a security flaw found in Ansible Engine when managing kubernetes using the k8s module.

2

Which versions of Ansible are affected by CVE-2020-1753?

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 are affected by CVE-2020-1753.

3

What is the severity of CVE-2020-1753?

CVE-2020-1753 has a severity value of 4, which is considered medium.

4

How can I fix CVE-2020-1753?

To fix CVE-2020-1753, update Ansible to version 2.7.18, 2.8.11, or 2.9.7 depending on the version you are using.

5

Where can I find more information about CVE-2020-1753?

You can find more information about CVE-2020-1753 in the following references: [Link 1](https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1811892), [Link 2](https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1811933), [Link 3](https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1811934).

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203