Skip to content
Fencer Intel
high 7.5

CVE-2020-13170 json

Improper Input Validation in HashiCorp Consul

published 6y ago modified 2mo ago also BIT-consul-2020-13170 , EUVD-2021-1142 , GHSA-p2j5-3f4c-224r , GO-2022-0859

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.8%
EPSS 1.8% chance of exploitation in 30 days, percentile 78%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/hashicorp/consul 1.6.6, 1.7.4
  • bitnami consul 1.6.6, 1.7.4
  • hashicorp consul 1.6.6, 1.7.4
  • consul Debian 11 1.7.4+dfsg1-1

debian advisories DEBIAN-CVE-2020-13170

Is CVE-2020-13170 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.77% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N
OSV 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
go github.com/hashicorp/consul
>=1.6.0-beta1, <1.6.6
>=1.7.0, <1.7.4
1.6.6
1.7.4
bitnami consul
>=1.4.0, <1.6.6
>=1.7.0, <1.7.4
1.6.6
1.7.4

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.