Hashicorp Consul 1.4.2

CPE Details

Hashicorp Consul 1.4.2
1.4.2
2020-02-28 14:52 +00:00
2021-02-09 16:58 +00:00

Alerte pour un CPE

Stay informed of any changes for a specific CPE.
Alert management

CPE Name: cpe:2.3:a:hashicorp:consul:1.4.2:*:*:*:*:*:*:*

Informations

Vendor

hashicorp

Product

consul

Version

1.4.2

Related CVE

Open and find in CVE List

CVE ID Published Description Score Severity
CVE-2020-13170 2020-06-11 17:41 +00:00 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.
7.5
HIGH
CVE-2020-12797 2020-06-11 17:37 +00:00 HashiCorp Consul and Consul Enterprise failed to enforce changes to legacy ACL token rules due to non-propagation to secondary data centers. Introduced in 1.4.0, fixed in 1.6.6 and 1.7.4.
5.3
MEDIUM
CVE-2020-13250 2020-06-11 17:16 +00:00 HashiCorp Consul and Consul Enterprise include an HTTP API (introduced in 1.2.0) and DNS (introduced in 1.4.3) caching feature that was vulnerable to denial of service. Fixed in 1.6.6 and 1.7.4.
7.5
HIGH
CVE-2020-7219 2020-01-31 11:39 +00:00 HashiCorp Consul and Consul Enterprise up to 1.6.2 HTTP/RPC services allowed unbounded resource usage, and were susceptible to unauthenticated denial of service. Fixed in 1.6.3.
7.5
HIGH
CVE-2020-7955 2020-01-31 11:19 +00:00 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.
5.3
MEDIUM
CVE-2019-12291 2019-06-06 14:35 +00:00 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.
7.5
HIGH