CVE-2020-1753

MEDIUMNVD 5.05.0
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.0 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 84% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 1%CVSS: 5.0Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.0
EG Score
5.0(medium)
EPSS
39.6%
KEV
Not listed

Published

March 16, 2020

Last Modified

November 21, 2024

References (14)

Vendor Advisories for CVE-2020-1753(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatansible-0:2.8.16-1.el8ae2020-10-06redhat
redhatansible-0:2.7.18-1.el7ae2020-05-13redhat
redhatansible-0:2.9.7-1.el8ae2020-04-22redhat
redhatansible-tower-35/ansible-tower:3.5.6-12020-04-22redhat
redhatansible-tower-37/ansible-tower-memcached-rhel7:1.4.15-282020-02-18redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
ansible1.0 ... 2.9.6 (171 versions)2.9.7

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(4)

Frequently asked(5)

What is CVE-2020-1753?
CVE-2020-1753 is a medium vulnerability published on March 16, 2020. 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…
When was CVE-2020-1753 disclosed?
CVE-2020-1753 was first published in the National Vulnerability Database on March 16, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-1753 actively exploited?
CVE-2020-1753 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 39.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2020-1753?
CVE-2020-1753 has a CVSS v3 base score of 5.0 (NVD).
How do I remediate CVE-2020-1753?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-1753, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-1753

Explore →

Is Your Infrastructure Affected by CVE-2020-1753?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.