CVE-2019-12291 json
HashiCorp Consul Incorrect Access Control vulnerability
published 7y ago modified 4mo ago also GHSA-h65h-v7fw-4p38 , GO-2023-1852 , EUVD-2023-1815
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 67%
- public exploits
- 0
- none known
Summary
HashiCorp Consul 1.4.0 through 1.5.0 has Incorrect Access Control. Keys not matching a specific ACL rule used for prefix matching in a policy can be deleted by a token using that policy even with default deny settings configured.
Patch / fix
- go github.com/hashicorp/consul 1.5.1
- consul Debian 11 1.4.5+dfsg1-1
debian advisories DEBIAN-CVE-2019-12291
Is CVE-2019-12291 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.16% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 6.4 | AV:N/AC:L/Au:N/C:N/I:P/A:P |
| GitHub | 3.0 | 7.5 | CVSS:3.0/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.4.0, <1.5.1 |
1.5.1 |
Classification
- Weakness
-
- CWE-284 Improper Access Control
References
-
github.com
/hashicorp/consul/issues/5888
web, issue-tracking, mitigation, patch, third-party-advisory, report
-
github.com
/hashicorp/consul/commit/36ebca1fd0129278487c6570449bc8cc03987890
web, patch
-
nvd.nist.gov
/vuln/detail/CVE-2019-12291
advisory
-
github.com
/hashicorp/consul
package
-
hashicorp.com
/blog/category/consul
web
-
github.com
/advisories/GHSA-h65h-v7fw-4p38
advisory
Sources
- CVE List CVE-2019-12291
- GitHub Advisory GHSA-h65h-v7fw-4p38
- NVD CVE-2019-12291
- OSV GO-2023-1852
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.