dbcve.org
FedoraOperating system · Fedoraproject

CVE-2022-29153

HIGH · 7.5 CVSS v3.1 Published 2022-04-19
Fix available
A fix is available. Upgrade to 1.9.17 / 1.10.10 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 and Consul Enterprise up to 1.9.16, 1.10.9, and 1.11.4 may allow server side request forgery when the Consul client agent follows redirects returned by HTTP health check endpoints. Fixed in 1.9.17, 1.10.10, and 1.11.5.

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 and Consul Enterprise contain a server-side request forgery (SSRF) vulnerability where the client agent follows redirects returned by HTTP health check endpoints. An attacker controlling or compromising an HTTP health check endpoint could redirect the Consul client to make arbitrary HTTP requests to internal services.

MitigationUpgrade Consul to versions 1.9.17, 1.10.10, or 1.11.5 or later. If immediate upgrade is not possible, review and restrict HTTP health check configurations to trusted endpoints.

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
FedoraOperating system
Affected:= 37
ConsulApplication
Affected:< 1.9.17>= 1.10.0, < 1.10.10>= 1.11.0, < 1.11.5

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Determine Consul version
    Run `consul --version` to obtain the installed version. If using a package manager, also check with `rpm -q consul` or `dpkg -l consul` depending on your OS.
    Affected if The version falls within any of these ranges: < 1.9.17, >= 1.10.0 and < 1.10.10, or >= 1.11.0 and < 1.11.5. Compare your version number against these affected ranges.
  2. Identify Consul configuration files
    Locate Consul configuration files. Common locations include `/etc/consul/consul.hcl`, `/etc/consul.d/*.hcl`, or the directory specified by the `-config-dir` flag. Check your Consul process: `ps aux | grep consul` to find the actual configuration path.
    Affected if Configuration files exist and the Consul service is running.
  3. Detect HTTP health check definitions
    Search configuration files for health check definitions of type `http`. Look for blocks containing `check {` with `type = "http"` or `http = "<URL>"` syntax. Use grep: `grep -r "http.*health" /etc/consul/` or inspect the service definitions in the Consul UI or API: `curl localhost:8500/v1/health/service/<service-name>`
    Affected if Any HTTP-type health check endpoint is configured. The vulnerability only applies when HTTP health checks are defined.
  4. Inspect HTTP health check target URLs
    Review each HTTP health check definition and extract the target URL. Check if the endpoint is hosted on an untrusted or publicly accessible server, or if it could be compromised. Look for URLs using internal IP addresses or private hostnames that should not be exposed.
    Affected if The HTTP health check URL points to a service or endpoint that is not fully trusted, is externally accessible, or could be controlled by an attacker.

You are affected if your Consul version is below 1.9.17, between 1.10.0-1.10.9, or between 1.11.0-1.11.4, AND you have HTTP health checks configured that could be controlled by an untrusted party.

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.17 / 1.10.10 / 1.11.5 or later
Fixed in 1.9.171.10.101.11.5
Interim mitigation

Upgrade Consul to versions 1.9.17, 1.10.10, or 1.11.5 or later. If immediate upgrade is not possible, review and restrict HTTP health check configurations to trusted endpoints.

Recommended fix High confidence

Consul 1.9.17, 1.10.10, or 1.11.5 depending on your current version branch

  1. 1. Identify current Consul version by running `consul --version`
  2. 2. Determine which version line you are on (1.9.x, 1.10.x, or 1.11.x)
  3. 3. If on 1.9.x line, upgrade to version 1.9.17
  4. 4. If on 1.10.x line, upgrade to version 1.10.10
  5. 5. If on 1.11.x line, upgrade to version 1.11.5
  6. 6. Download the appropriate Consul binary from https://www.consul.io/downloads
  7. 7. Stop the Consul service on all nodes
  8. 8. Replace the Consul binary with the new version
Caveat Review Consul upgrade notes for your version path - some upgrades may require careful handling of raft protocol versions

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

Fix this in Fedora Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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