ChainPyPI:ansible
ansible: successive fixes (2021)
3 CVEs over 2 generations, 26 May 2021 to 16 Mar 2022.
Family tree
Left to right by publication date.Oldest first. Select a CVE to open it.- CVE-2021-2017826 May 2021 next fix after CVE-2021-20191
- CVE-2021-2019126 May 2021 No direct link to an earlier CVE
- CVE-2021-2018016 Mar 2022 next fix after CVE-2021-20191
Exploited in the wild (CISA KEV) Not in KEV Priority score (0 to 100) High confidence Medium Low Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
CVEs in this family
Table view of the tree| CVE | Published | Title | Linked from | Priority |
|---|---|---|---|---|
| CVE-2021-20178 | 26 May 2021 | A flaw was found in ansible module where credentials are disclosed in the console log by default and not protected by… · fixed in 2.9.18 | CVE-2021-20191 · Next fix in the same package · Medium | 5.5 |
| CVE-2021-20191 | 26 May 2021 | A flaw was found in ansible · fixed in 2.10.7 | First in chain | 5.7 |
| CVE-2021-20180 | 16 Mar 2022 | A flaw was found in ansible module where credentials are disclosed in the console log by default and not protected by… · fixed in 2.9.18 | CVE-2021-20191 · Next fix in the same package · Medium | 4.9 |