dbcve.org
ConsulApplication · Hashicorp

CVE-2022-24687

MEDIUM · 6.5 CVSS v3.1 Published 2022-02-24
Fix available
A fix is available. Upgrade to 1.9.15 / 1.10.8 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
HashiCorp Consul and Consul Enterprise 1.9.0 through 1.9.14, 1.10.7, and 1.11.2 clusters with at least one Ingress Gateway allow a user with service:write to register a specifically-defined service that can cause Consul servers to panic. Fixed in 1.9.15, 1.10.8, and 1.11.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 · high confidence

A user with service:write permissions on Consul clusters (versions 1.9.0-1.9.14, 1.10.7, 1.11.2) that have at least one Ingress Gateway can register a specifically-crafted service that triggers a panic in Consul servers, causing denial of service.

MitigationUpgrade Consul to version 1.9.15, 1.10.8, 1.11.3 or later. Until patched, restrict service:write permissions to trusted operators only.

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
ConsulApplication
Affected:>= 1.8.0, < 1.9.15>= 1.10.0, < 1.10.8>= 1.11.0, < 1.11.3

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Consul server version
    Run `consul version` on each server node to get the Consul version. Alternatively, query the /v1/agent/self API endpoint on any agent.
    Affected if The version falls within these ranges: 1.9.0-1.9.14, 1.10.0-1.10.7, 1.11.0-1.11.2, or any version >=1.8.0 but <1.9.15, <1.10.8, or <1.11.3.
  2. Verify Ingress Gateway configuration exists
    Query the Consul catalog or configuration: run `consul catalog services` to list services, then check for ingress-gateway service type using `consul config read -kind ingress-gateway` or query the /v1/config/ingress-gateway API endpoint.
    Affected if At least one Ingress Gateway service is registered or configured in the cluster.
  3. Check for service:write ACL permissions
    Review ACL policies: run `consul acl policy list` to see available policies, then inspect policies with `consul acl policy read -name <policy_name>` or query /v1/acl/policies. Look for policies granting `service:write` permissions.
    Affected if Any ACL policy or token grants service:write permission to users other than full administrators.
  4. Identify non-admin users with service:write
    Examine ACL tokens: run `consul acl token list` and review associated policies. Cross-reference tokens with service:write policies identified in the previous step.
    Affected if There are active tokens (excluding anonymous token) bound to policies that grant service:write permissions.

Your environment is affected if you run a vulnerable Consul version, have an Ingress Gateway configured, and have any user or token with service:write permissions that could register a malicious service.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.9.15 / 1.10.8 / 1.11.3 or later
Fixed in 1.9.151.10.81.11.3
Interim mitigation

Upgrade Consul to version 1.9.15, 1.10.8, 1.11.3 or later. Until patched, restrict service:write permissions to trusted operators only.

Recommended fix High confidence

Upgrade to 1.9.15, 1.10.8, or 1.11.3 depending on current version branch

  1. 1. Identify the current Consul version by running `consul --version`
  2. 2. Determine which upgrade path applies based on current version: if on 1.9.x upgrade to 1.9.15; if on 1.10.x upgrade to 1.10.8; if on 1.11.x upgrade to 1.11.3
  3. 3. Back up Consul data directory and configuration files before upgrading
  4. 4. For Consul servers, upgrade each node one at a time, ensuring cluster quorum is maintained
  5. 5. After upgrading all server nodes, upgrade any client nodes
  6. 6. Verify Consul is running and the cluster is healthy with `consul members` and `consul operator raft list-peers`
  7. 7. Confirm the panic issue is resolved by testing Ingress Gateway service registration with a user that has service:write permissions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Consul Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-24687 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-24687 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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