CVE-2022-3920
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 · uneditedHashiCorp Consul and Consul Enterprise 1.13.0 up to 1.13.3 do not filter cluster filtering's imported nodes and services for HTTP or RPC endpoints used by the UI. Fixed in 1.14.0.
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 · high confidenceConsul's cluster filtering does not properly filter imported nodes and services for HTTP or RPC endpoints used by the UI. This allows unauthorized access to services and nodes that should be isolated through Consul's cluster peering or network areas feature, potentially exposing cross-cluster service data to unauthorized users.
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.13.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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 check the Consul binary version to determine the installed versionAffected if Version is >= 1.13.0 and <= 1.13.3
-
Verify cluster peering is configuredRun 'consul peering list' or check for peering configurations via API at /v1/peeringsAffected if Any cluster peering relationships exist between Consul datacenters
-
Verify network areas are configuredRun 'consul operator area list' or check for network area configurations via API at /v1/status/leaderAffected if Any network areas are configured for cross-datacenter communication
-
Confirm UI access is enabledCheck if the Consul UI is accessible via HTTP on ports 8500 or 8501, or verify UI configuration in consul.hclAffected if UI HTTP or RPC endpoints are accessible to users
-
Check for cross-cluster service queriesReview access logs or audit logs for queries to services that may exist across peered clusters or network areasAffected if Cross-cluster service queries have been performed via the UI
A Consul installation is affected if it runs version 1.13.0 through 1.13.3 AND has cluster peering or network areas configured with UI access enabled.
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 · scopedUpgrade Consul and Consul Enterprise to version 1.14.0 or later to apply the fix that properly filters cluster-filtered imported nodes and services for UI endpoints.
Consul 1.14.0
- Back up Consul data directory and configuration files before upgrading
- Stop the running Consul service
- Download Consul version 1.14.0 from the official HashiCorp releases (https://www.consul.io/downloads)
- Replace the existing Consul binary with the new 1.14.0 binary
- Verify the Consul binary version is 1.14.0 using 'consul version'
- Start the Consul service
- Verify the upgrade was successful by checking Consul status and ensuring the UI loads correctly
- Confirm that cluster filtering now properly filters imported nodes and services for HTTP/RPC endpoints used by the UI
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3920 — 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-2022-3920 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