ChainGo:github.com/hashicorp/vault
github.com/hashicorp/vault: related fixes (2020)
3 CVEs over 2 generations, 23 Mar 2020 to 30 Sep 2020.
Family tree
Left to right by publication date.Oldest first. Select a CVE to open it.- CVE-2020-1066023 Mar 2020 First in the chain
- CVE-2020-1066123 Mar 2020 No direct link to an earlier CVE
- CVE-2020-2581630 Sep 2020 related to CVE-2020-10660related to CVE-2020-10661
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-2020-10660 | 23 Mar 2020 | HashiCorp Vault and Vault Enterprise versions 0.9.0 through 1.3.3 may, under certain circumstances, have an Entity's… · fixed in 1.3.4 | First in chain | 11.1 |
| CVE-2020-10661 | 23 Mar 2020 | HashiCorp Vault and Vault Enterprise versions 0.11.0 through 1.3.3 may, under certain circumstances, have existing… · fixed in 1.3.4 | First in chain | 13.2 |
| CVE-2020-25816 | 30 Sep 2020 | HashiCorp Vault and Vault Enterprise versions 1.0 and newer allowed leases created with a batch token to outlive their… · fixed in 1.5.4 | CVE-2020-10660 · related · Medium | 12.6 |