CVE-2020-28053 json
Privilege Escalation in HashiCorp Consul
published 5y ago modified 2mo ago also BIT-consul-2020-28053 , EUVD-2024-0275 , GHSA-6m72-467w-94rh , GO-2024-2505
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.5%
- EPSS 1.5% chance of exploitation in 30 days, percentile 73%
- public exploits
- 0
- none known
Summary
HashiCorp Consul and Consul Enterprise 1.2.0 up to 1.8.5 allowed operators with operator:read ACL permissions to read the Connect CA private key configuration. Fixed in 1.6.10, 1.7.10, and 1.8.6.
Patch / fix
- go github.com/hashicorp/consul 1.6.10, 1.7.10, 1.8.6
- bitnami consul 1.6.10, 1.7.10, 1.8.6
- hashicorp consul 1.6.10, 1.7.10, 1.8.6
- consul Debian 11 1.8.6+dfsg1-1
debian advisories DEBIAN-CVE-2020-28053
- consul Arch Linux 1.9.1-1
arch linux advisories AVG-1294
- github.com/hashicorp/consul@ff5215d commit
- github.com/hashicorp/consul#9240 pull request
Is CVE-2020-28053 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 FencerExploit prediction
1.45% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
| OSV | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/hashicorp/consul | >=1.2.0, <1.6.10 >=1.7.0, <1.7.10 >=1.8.0, <1.8.6 |
1.6.10 1.7.10 1.8.6 |
| bitnami | consul | >=1.2.0, <1.6.10 >=1.7.0, <1.7.10 >=1.8.0, <1.8.6 |
1.6.10 1.7.10 1.8.6 |
Classification
References
-
github.com
/hashicorp/consul/pull/9240
web, patch
-
github.com
/hashicorp/consul/commit/ff5215d882ac51b49c2647aac46b42aa9c890ce3
web, patch
-
security.gentoo.org
/glsa/202208-09
vendor-advisory, web, third-party-advisory, advisory
-
hashicorp.com
/blog/category/consul
web, product, vendor-advisory, advisory
-
github.com
/hashicorp/consul/blob/master/CHANGELOG.md#186-november-19-2020
web, release-notes, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-28053
advisory, web
-
github.com
/advisories/GHSA-6m72-467w-94rh
advisory
Sources
- CVE List CVE-2020-28053
- GitHub Advisory GHSA-6m72-467w-94rh
- NVD CVE-2020-28053
- OSV BIT-consul-2020-28053
- OSV GO-2024-2505
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.