dbcve.org
Consul TemplateApplication · Hashicorp

CVE-2022-38149

HIGH · 7.5 CVSS v3.1 Published 2022-08-17
Fix available
A fix is available. Upgrade to 0.29.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 Template up to 0.27.2, 0.28.2, and 0.29.1 may expose the contents of Vault secrets in the error returned by the *template.Template.Execute method, when given a template using Vault secret contents incorrectly. Fixed in 0.27.3, 0.28.3, and 0.29.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 Template leaks Vault secret contents into error messages returned by the template.Template.Execute method when templates use Vault secret contents incorrectly. This information disclosure vulnerability has a CVSS 7.5 (HIGH) rating.

MitigationUpgrade Consul Template to version 0.27.3, 0.28.3, or 0.29.2 or later to prevent Vault secrets from being exposed in error messages.

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
Consul TemplateApplication
Affected:< 0.29.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
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 checks

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

  1. Determine Consul Template version
    Run `consul-template -version` or check the installed binary version to identify the exact version number
    Affected if Version is below 0.29.2 (including 0.29.1, 0.29.0, 0.28.x versions before 0.28.3, and 0.27.x versions before 0.27.3)
  2. Verify Vault integration is in use
    Inspect your Consul Template configuration files for vault stanza blocks or template files that reference Vault secrets using the vault secret or vault kv paths
    Affected if Consul Template is configured to fetch secrets from Vault and render them into templates
  3. Identify templates using Vault secrets
    Review all template files (.tmpl) processed by Consul Template for references to Vault secret paths or KV engine endpoints
    Affected if Templates contain vault() function calls or secret references that pull data from Vault
  4. Check for template execution errors
    Monitor Consul Template logs and output for error messages generated during template rendering, especially errors related to vault secret access or template syntax
    Affected if Template errors occur during execution and the environment uses Vault-backed secrets in templates

You are affected if Consul Template version is below 0.29.2 and templates are configured to fetch and render Vault secrets, as secret contents may be exposed in any error messages produced during template execution.

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 0.29.2 or later
Fixed in 0.29.2
Interim mitigation

Upgrade Consul Template to version 0.27.3, 0.28.3, or 0.29.2 or later to prevent Vault secrets from being exposed in error messages.

Recommended fix High confidence

Consul Template 0.29.2 (or 0.28.3/0.27.3 for respective version branches)

  1. 1. Identify current Consul Template version by running `consul-template --version`
  2. 2. Review current template configurations for any Vault secret usage
  3. 3. Download Consul Template version 0.29.2 (or 0.28.3/0.27.3 if staying on older major branches) from https://releases.hashicorp.com/consul-template/
  4. 4. Install the new version following standard installation procedures for your environment
  5. 5. Validate templates do not incorrectly use Vault secret contents in ways that could trigger the vulnerable error path
  6. 6. Restart Consul Template service with the new version
  7. 7. Verify the application functions correctly and no sensitive data appears in logs
Caveat Review release notes for any template syntax or behavior changes between versions; minor version upgrades typically have minimal breaking changes

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

Fix this in Consul Template Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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