Skip to content
Fencer Vulns
medium 5.3

CVE-2020-7955 json

Incorrect Authorization in HashiCorp Consul

published 2020-01-31 6 y ago modified 2026-09-08 2 mo ago also BIT-consul-2020-7955 , EUVD-2021-1487 , GHSA-r9w6-rhh9-7v53 , GO-2022-0874

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

Summary

HashiCorp Consul and Consul Enterprise 1.4.1 through 1.6.2 did not uniformly enforce ACLs across all API endpoints, resulting in potential unintended information disclosure. Fixed in 1.6.3.

Patch / fix

  • go github.com/hashicorp/consul 1.6.3
  • bitnami consul 1.6.2
  • hashicorp consul 1.6.2
  • consul Debian 11 1.7.0+dfsg1-1

debian advisories DEBIAN-CVE-2020-7955

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-7955 updated cvss 5.3

consul: Missing access control in HTTP API endpoints

  • Red Hat OpenShift Service Mesh 1 servicemesh, servicemesh-mixc, servicemesh-mixs, servicemesh-galley, servicemesh-citadel, servicemesh-istioctl, +5 more Red Hat Fuse 7 consul-client consul-client
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.41% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-08).

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 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N
OSV 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/hashicorp/consul
>=1.4.1, <1.6.3
1.6.3
bitnami consul
>=1.4.1, <1.6.2
1.6.2

Classification

Weakness

References

Sources

Fencer Vulns 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.