ChainGo:github.com/hashicorp/consul
github.com/hashicorp/consul: related fixes (2018–2021)
3 CVEs over 3 generations, 9 Dec 2018 to 7 Sep 2021.
Family tree
Left to right by publication date.Oldest first. Select a CVE to open it.- CVE-2018-196539 Dec 2018 First in the chain
- CVE-2019-976426 Mar 2019 related to CVE-2018-19653
- CVE-2021-372197 Sep 2021 related to CVE-2018-19653related to CVE-2019-9764
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-2018-19653 | 9 Dec 2018 | HashiCorp Consul 0.5.1 through 1.4.0 can use cleartext agent-to-agent RPC communication because the verify_outgoing… · fixed in 1.4.1 | First in chain | 13.7 |
| CVE-2019-9764 | 26 Mar 2019 | HashiCorp Consul 1.4.3 lacks server hostname verification for agent-to-agent TLS communication · fixed in 1.4.4 | CVE-2018-19653 · related · Medium | 9.8 |
| CVE-2021-37219 | 7 Sep 2021 | HashiCorp Consul and Consul Enterprise 1.10.1 Raft RPC layer allows non-server agents with a valid certificate signed… · fixed in 1.10.2 | CVE-2018-19653 · related · Medium | 13.4 |