dbcve.org
ConsulApplication · Hashicorp

CVE-2022-40716

MEDIUM · 6.5 CVSS v3.1 Published 2022-09-23
Fix available
A fix is available. Upgrade to 1.11.9 / 1.12.5 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 up to 1.11.8, 1.12.4, and 1.13.1 do not check for multiple SAN URI values in a CSR on the internal RPC endpoint, enabling leverage of privileged access to bypass service mesh intentions. Fixed in 1.11.9, 1.12.5, and 1.13.2."

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

HashiCorp Consul fails to validate multiple SAN URI values in Certificate Signing Requests (CSRs) submitted to the internal RPC endpoint. This allows authenticated, privileged users to potentially bypass service mesh intentions by crafting CSRs with multiple SAN URIs, leveraging their privileged access to impersonate services.

MitigationUpgrade Consul and Consul Enterprise to versions 1.11.9, 1.12.5, or 1.13.2 or later to patch the CSR validation vulnerability on the internal RPC endpoint.

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.11.9>= 1.12.0, < 1.12.5>= 1.13.0, < 1.13.2

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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 checks

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

  1. Check Consul version
    Run `consul version` or inspect the Consul process/version file to obtain the installed version number
    Affected if The installed version falls within < 1.11.9, >= 1.12.0 and < 1.12.5, or >= 1.13.0 and < 1.13.2
  2. Verify Consul Connect service mesh is enabled
    Check for the presence of the Connect subsystem: run `consul connect` command, check configuration files for `connect` stanza, or query the Consul API at `/v1/agent/connect`
    Affected if Consul Connect service mesh is enabled and the Consul version is vulnerable
  3. Confirm RPC endpoint accessibility
    Check if the Consul RPC port (default 8300) is accessible to untrusted users, or review ACL policies for access to the `/v1/agent/connect/authorize` RPC endpoint
    Affected if The internal RPC endpoint is accessible to authenticated, privileged users who could submit malicious CSRs
  4. Review certificate signing request logs or audit trails
    Examine Consul logs for certificate issuance events, particularly CSRs containing multiple `subjectAltName` URI entries, or inspect the Consul CA configuration for patterns of multi-URI certificate requests
    Affected if Multiple SAN URI values appear in CSRs submitted to the internal RPC endpoint, indicating exploitation attempts

You are affected if Consul Connect service mesh is enabled and the installed version is one of the vulnerable releases listed in the affected version ranges.

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.11.9 / 1.12.5 / 1.13.2 or later
Fixed in 1.11.91.12.51.13.2
Interim mitigation

Upgrade Consul and Consul Enterprise to versions 1.11.9, 1.12.5, or 1.13.2 or later to patch the CSR validation vulnerability on the internal RPC endpoint.

Recommended fix High confidence

1.11.9, 1.12.5, or 1.13.2 (depending on current version branch)

  1. 1. Identify current Consul version by running `consul version`
  2. 2. Determine target upgrade version based on current version branch: if on 1.11.x upgrade to 1.11.9; if on 1.12.x upgrade to 1.12.5; if on 1.13.x upgrade to 1.13.2
  3. 3. Review Consul upgrade documentation at https://www.consul.io/docs/upgrading
  4. 4. Back up Consul data directory and configuration files before upgrading
  5. 5. Stop Consul service on all nodes
  6. 6. Install the target fixed version using package manager or manual binary replacement
  7. 7. Restart Consul service on all nodes
  8. 8. Verify upgrade by running `consul version` and checking cluster health with `consul members`
Caveat Review Consul 1.11, 1.12, and 1.13 release notes for any breaking changes or migration requirements before upgrading

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

Fix this in Consul Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-40716 — 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-40716 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