CVE-2023-1297
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedConsul 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
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceConsul's cluster peering implementation had a logic flaw where a peer cluster registering a service with the same name as a local service could corrupt Consul's internal state, causing a denial of service condition. This state corruption affects the cluster's ability to properly route and manage services.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 1.13.0, < 1.14.7>= 1.15.0, < 1.15.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Consul versionRun 'consul --version' or query the /v1/agent/self API endpoint to retrieve the installed Consul versionAffected if Version is >= 1.13.0 and < 1.14.7, or >= 1.15.0 and < 1.15.3
-
Verify cluster peering is enabledCheck Consul configuration files or run 'consul operator peering list' to see if any peerings existAffected if Cluster peering is active with at least one peer cluster
-
List local registered servicesRun 'consul catalog services' or query /v1/catalog/services to obtain all services registered in the local clusterAffected if Any services are registered locally
-
Identify peer cluster servicesRun 'consul catalog services -peers' or query peer cluster service registrations to see what services are exposed from peer clustersAffected if Services from peer clusters share the same names as local services
You are affected if your Consul version falls within the vulnerable ranges AND cluster peering is enabled AND a peer cluster has registered a service with an identical name to a local service.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.14.71.15.3
Upgrade Consul to version 1.14.5, 1.15.3, or later to resolve this vulnerability. Prior to upgrading, assess current cluster peering configurations and plan for testing service connectivity post-upgrade.
Consul 1.14.7 (for 1.14.x branch) or Consul 1.15.3 (for 1.15.x branch)
- 1. Identify current Consul version by checking the Consul process or configuration
- 2. Determine which branch of Consul you are running (1.14.x or 1.15.x)
- 3. For Consul 1.14.x branch: Upgrade to Consul 1.14.7 or later
- 4. For Consul 1.15.x branch: Upgrade to Consul 1.15.3 or later
- 5. After upgrading, verify cluster health using 'consul members' or 'consul operator raft list-peers'
- 6. Test cluster peering functionality to ensure the vulnerability is mitigated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-1297 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-1297 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data