CVE-2023-1297GO-2023-1827BIT-CONSUL-2023-1297GHSA-C57C-7HRJ-6Q6V
Consul Cluster Peering can Result in Denial of Service
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.14.5, 1.15.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Consul and Consul Enterprise's cluster peering implementation contained a flaw whereby a peer cluster with service of the same name as a local service could corrupt Consul state, resulting in denial of service. This vulnerability was resolved in Consul 1.14.5, and 1.15.3
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- HashiCorp Consul
From 1.14.0 · through 1.14.5; From 1.15.0 · through 1.15.3
- HashiCorp Consul Enterprise
From 1.14.0 · through 1.14.5; From 1.15.0 · through 1.15.3
- github.com/hashicorp/consulGo
fixed in 1.14.5; From 1.15.0 · fixed in 1.15.3
- github.com/hashicorp/consulGo
fixed in 1.14.5
- github.com/hashicorp/consulGo
From 1.15.0 · fixed in 1.15.3