Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2020-13170: HashiCorp Consul and Consul Enterprise did not appropriately enforce scope for local tokens issued by a primar

51
This month
HIGH 7.5REMOTEUPGRADE

CVE-2020-13170 is a high-severity flaw (CVSS 7.5) affecting consul. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

HashiCorp Consul and Consul Enterprise did not appropriately enforce scope for local tokens issued by a primary data center, where replication to a secondary data center was not enabled. Introduced in 1.4.0, fixed in 1.6.6 and 1.7.4.

Why this priority

  • High severity
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score7.5 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance1.8% (top 22%)
CISA exploited listNo
WeaknessCWE-20
Published2020-06-11
Last modified2026-06-17
Publisher (CNA): MITRE · Vendor: hashicorp

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

hashicorp consul UPGRADE
Affected: >= 1.4.0 and < 1.6.6 · >= 1.7.0 and < 1.7.4
Fixed in: 1.6.6, 1.7.4
Safe to downgrade to: a release before 1.4.0
1. Check installed version
apt-cache policy consul || rpm -q consul || consul --version
2. UPGRADE to 1.6.6 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade consul
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade consul
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 1.4.0 (Debian / Ubuntu)
apt-cache madison consul sudo apt install consul=<VERSION_BEFORE_1.4.0> sudo apt-mark hold consul
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list consul sudo dnf downgrade consul-<VERSION_BEFORE_1.4.0> sudo dnf versionlock add consul
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-13170?

consul: upgrade to 1.6.6, 1.7.4. Exact commands for each OS are on this page.

Is CVE-2020-13170 being exploited?

CVE-2020-13170 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-13170 affect?

CVE-2020-13170 affects consul. Severity is high (CVSS 7.5). HashiCorp Consul and Consul Enterprise did not appropriately enforce scope for local tokens issued by a primary data center, where replication to a secondary data center was not enabled. Introduced in 1.4.0, fixed in 1.6.6 and 1.7.4.

How urgent is CVE-2020-13170?

Priority 51/100. High severity; Remotely exploitable, no login, no user action

Software pages

Consul vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.