CVE-2020-7219
- EPSS 0.87%
- Veröffentlicht 31.01.2020 13:15:10
- Zuletzt bearbeitet 21.11.2024 05:36:51
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.
CVE-2019-12291
- EPSS 0.42%
- Veröffentlicht 06.06.2019 17:29:00
- Zuletzt bearbeitet 21.11.2024 04:22:34
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.
CVE-2019-9764
- EPSS 0.18%
- Veröffentlicht 26.03.2019 14:29:00
- Zuletzt bearbeitet 21.11.2024 04:52:16
HashiCorp Consul 1.4.3 lacks server hostname verification for agent-to-agent TLS communication. In other words, the product behaves as if verify_server_hostname were set to false, even when it is actually set to true. This is fixed in 1.4.4.
CVE-2019-8336
- EPSS 0.36%
- Veröffentlicht 05.03.2019 23:29:02
- Zuletzt bearbeitet 21.11.2024 04:49:42
HashiCorp Consul (and Consul Enterprise) 1.4.x before 1.4.3 allows a client to bypass intended access restrictions and obtain the privileges of one other arbitrary token within secondary datacenters, because a token with literally "<hidden>" as its s...
CVE-2018-19653
- EPSS 0.43%
- Veröffentlicht 09.12.2018 19:29:00
- Zuletzt bearbeitet 21.11.2024 03:58:21
HashiCorp Consul 0.5.1 through 1.4.0 can use cleartext agent-to-agent RPC communication because the verify_outgoing setting is improperly documented. NOTE: the vendor has provided reconfiguration steps that do not require a software upgrade.