dbcve.org
ConsulApplication · Hashicorp

CVE-2020-7219

HIGH · 7.5 CVSS v3.1 Published 2020-01-31
Fix available
A fix is available. Upgrade to 1.6.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 and Consul Enterprise up to 1.6.2 HTTP/RPC services allowed unbounded resource usage, and were susceptible to unauthenticated denial of service. Fixed in 1.6.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

HashiCorp Consul and Consul Enterprise up to version 1.6.2 had unbounded resource usage in HTTP/RPC services, allowing unauthenticated attackers to cause denial of service by consuming excessive server resources without any credentials.

MitigationUpgrade Consul and Consul Enterprise to version 1.6.3 or later to receive the resource limiting and authentication fixes.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 version
    Run `consul --version` or check the Consul binary metadata to determine the installed version
    Affected if Version is below 1.6.2 (including 1.6.0, 1.6.1, 1.5.x, 1.4.x and earlier)
  2. Verify HTTP API port exposure
    Check if port 8500 (default HTTP API port) is listening and accessible from untrusted networks using `netstat -tlnp` or similar network inspection
    Affected if HTTP API port is exposed to unauthenticated/untrusted network segments
  3. Verify RPC port exposure
    Check if ports 8300-8302 (default RPC and Serf ports) are listening and accessible from untrusted networks
    Affected if RPC ports are exposed to unauthenticated/untrusted network segments
  4. Confirm RPC service accessibility
    Test RPC endpoint availability using tools like `nc` or `telnet` to attempt connection to Consul RPC port from an untrusted host without credentials
    Affected if RPC service accepts connections without authentication from untrusted hosts

Environment is affected if Consul version is below 1.6.2 AND the HTTP API (port 8500) or RPC ports are accessible to unauthenticated attackers on untrusted networks.

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.

From vendor data
Upgrade available Upgrade to 1.6.2 or later
Fixed in 1.6.2
Interim mitigation

Upgrade Consul and Consul Enterprise to version 1.6.3 or later to receive the resource limiting and authentication fixes.

Fix this in Consul Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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