Latest hashicorp consul Vulnerabilities

● CVE-2023-5332
Configuration in GitLab
GitLab GitLab>=9.5.0<16.2.8
GitLab GitLab>=16.3.0<16.3.5
GitLab GitLab=16.4.0
HashiCorp Consul<0.9.4
HashiCorp Consul>=1.0.0<1.0.8
HashiCorp Consul>=1.2.0<1.2.4
and 1 more
● CVE-2023-3518
A vulnerability was identified in Consul such that using JWT authentication for service mesh incorrectly allows/denies access regardless of service identities. This vulnerability, CVE-2023-3518, affec...
HashiCorp Consul=1.16.0
HashiCorp Consul=1.16.0
HashiCorp Consul=1.16.0-rc1
go/github.com/hashicorp/consul=1.16.0
● CVE-2023-2816
Consul and Consul Enterprise allowed any user with service:write permissions to use Envoy extensions configured via service-defaults to patch remote proxy instances that target the configured service,...
HashiCorp Consul>=1.15.0<1.15.3
HashiCorp Consul>=1.15.0<1.15.3
● CVE-2023-1297
Consul and Consul Enterprise's cluster peering implementation contained a flaw whereby a peer cluster with service of the same name as a local service could corrupt Consul state, resulting in denial o...
HashiCorp Consul>=1.13.0<1.14.7
HashiCorp Consul>=1.13.0<1.14.7
HashiCorp Consul>=1.15.0<1.15.3
HashiCorp Consul>=1.15.0<1.15.3
● CVE-2023-0845
Consul and Consul Enterprise allowed an authenticated user with service:write permissions to trigger a workflow that causes Consul server and client agents to crash under certain circumstances. This v...
HashiCorp Consul<1.14.5
go/github.com/hashicorp/consul>=1.14.0<1.14.5
● CVE-2022-3920
HashiCorp Consul and Consul Enterprise 1.13.0 up to 1.13.3 do not filter cluster filtering's imported nodes and services for HTTP or RPC endpoints used by the UI. Fixed in 1.14.0.
HashiCorp Consul>=1.13.0<=1.13.3
HashiCorp Consul>=1.13.0<=1.13.3
● CVE-2022-40716
HashiCorp Consul and Consul Enterprise versions prior to 1.11.9, 1.12.5, and 1.13.2 do not check for multiple SAN URI values in a CSR on the internal RPC endpoint, enabling leverage of privileged acce...
go/github.com/hashicorp/consul>=1.13.0<1.13.2
go/github.com/hashicorp/consul>=1.12.0<1.12.5
go/github.com/hashicorp/consul<1.11.9
HashiCorp Consul<1.11.9
HashiCorp Consul<1.11.9
HashiCorp Consul>=1.12.0<1.12.5
and 3 more
● CVE-2021-41803
HashiCorp Consul 1.8.1 up to 1.11.8, 1.12.4, and 1.13.1 did not properly validate the node or segment names prior to interpolation and usage in JWT claim assertions with the auto config RPC. Fixed in ...
HashiCorp Consul>=1.8.1<1.11.9
HashiCorp Consul>=1.8.1<1.11.9
HashiCorp Consul=1.12.4
HashiCorp Consul=1.12.4
HashiCorp Consul=1.13.1
HashiCorp Consul=1.13.1
and 3 more
● CVE-2022-29153
HashiCorp Consul and Consul Enterprise up to 1.9.16, 1.10.9, and 1.11.4 may allow server side request forgery when the Consul client agent follows redirects returned by HTTP health check endpoints. Fi...
HashiCorp Consul<1.9.17
HashiCorp Consul<1.9.17
HashiCorp Consul>=1.10.0<1.10.10
HashiCorp Consul>=1.10.0<1.10.10
HashiCorp Consul>=1.11.0<1.11.5
HashiCorp Consul>=1.11.0<1.11.5
and 1 more
● CVE-2022-24687
HashiCorp Consul and Consul Enterprise 1.9.0 through 1.9.14, 1.10.7, and 1.11.2 clusters with at least one Ingress Gateway allow a user with service:write to register a specifically-defined service th...
HashiCorp Consul>=1.8.0<1.9.15
HashiCorp Consul>=1.8.0<1.9.15
HashiCorp Consul>=1.10.0<1.10.8
HashiCorp Consul>=1.10.0<1.10.8
HashiCorp Consul>=1.11.0<1.11.3
HashiCorp Consul>=1.11.0<1.11.3
● CVE-2021-41805
HashiCorp Consul Enterprise before 1.8.17, 1.9.x before 1.9.11, and 1.10.x before 1.10.4 has Incorrect Access Control. An ACL token (with the default operator:write permissions) in one namespace can b...
HashiCorp Consul>=1.7.0<1.8.17
HashiCorp Consul>=1.9.0<1.9.11
HashiCorp Consul>=1.10.0<1.10.4
● CVE-2021-38698
HashiCorp Consul and Consul Enterprise 1.10.1 Txn.Apply endpoint allowed services to register proxies for other services, enabling access to service traffic. Fixed in 1.8.15, 1.9.9 and 1.10.2.
HashiCorp Consul<1.8.15
HashiCorp Consul<1.8.15
HashiCorp Consul>=1.9.0<1.9.9
HashiCorp Consul>=1.9.0<1.9.9
HashiCorp Consul>=1.10.0<1.10.2
HashiCorp Consul>=1.10.0<1.10.2
● CVE-2021-37219
HashiCorp Consul and Consul Enterprise 1.10.1 Raft RPC layer allows non-server agents with a valid certificate signed by the same CA to access server-only functionality, enabling privilege escalation....
HashiCorp Consul<1.8.15
HashiCorp Consul<1.8.15
HashiCorp Consul>=1.9.0<1.9.9
HashiCorp Consul>=1.9.0<1.9.9
HashiCorp Consul>=1.10.0<1.10.2
HashiCorp Consul>=1.10.0<1.10.2
● CVE-2021-32574
HashiCorp Consul and Consul Enterprise 1.3.0 through 1.10.0 Envoy proxy TLS configuration does not validate destination service identity in the encoded subject alternative name. Fixed in 1.8.14, 1.9.8...
HashiCorp Consul>=1.3.0<1.8.14
HashiCorp Consul>=1.3.0<1.8.14
HashiCorp Consul>=1.9.0<1.9.8
HashiCorp Consul>=1.9.0<1.9.8
HashiCorp Consul>=1.10.0<1.10.1
HashiCorp Consul>=1.10.0<1.10.1
● CVE-2021-36213
HashiCorp Consul and Consul Enterprise 1.9.0 through 1.10.0 default deny policy with a single L7 application-aware intention deny action cancels out, causing the intention to incorrectly fail open, al...
HashiCorp Consul>=1.9.0<1.9.8
HashiCorp Consul>=1.9.0<1.9.8
HashiCorp Consul>=1.10.0<1.10.1
HashiCorp Consul>=1.10.0<1.10.1
● CVE-2020-25864
HashiCorp Consul and Consul Enterprise up to version 1.9.4 key-value (KV) raw mode was vulnerable to cross-site scripting. Fixed in 1.9.5, 1.8.10 and 1.7.14.
HashiCorp Consul<1.7.14
HashiCorp Consul<1.7.14
HashiCorp Consul>=1.8.0<1.8.10
HashiCorp Consul>=1.8.0<1.8.10
HashiCorp Consul>=1.9.0<1.9.5
HashiCorp Consul>=1.9.0<1.9.5
● CVE-2021-28156
HashiCorp Consul Enterprise version 1.8.0 up to 1.9.4 audit log can be bypassed by specifically crafted HTTP events. Fixed in 1.9.5, and 1.8.10.
HashiCorp Consul>=1.8.0<1.8.10
HashiCorp Consul>=1.9.0<1.9.5
● CVE-2021-3121
An issue was discovered in GoGo Protobuf before 1.3.2. plugin/unmarshal/unmarshal.go lacks certain index validation, aka the "skippy peanut butter" issue.
redhat/kiali<0:v1.24.7.redhat1-1.el8
redhat/cri-o<0:1.20.0-0.rhaos4.7.git8921e00.el8.51
redhat/cri-tools<0:1.20.0-1.el8
redhat/openshift-clients<0:4.7.0-202103251046.p0.git.3957.c4da68b.el7
redhat/openshift<0:4.8.0-202107161820.p0.git.051ac4f.assembly.stream.el8
redhat/openshift-clients<0:4.8.0-202106281541.p0.git.1077b05.assembly.stream.el8
and 8 more
● CVE-2020-28053
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.
HashiCorp Consul>=1.2.0<1.6.10
HashiCorp Consul>=1.2.0<1.6.10
HashiCorp Consul>=1.7.0<1.7.10
HashiCorp Consul>=1.7.0<1.7.10
HashiCorp Consul>=1.8.0<1.8.6
HashiCorp Consul>=1.8.0<1.8.6
and 3 more
● CVE-2020-25201
HashiCorp Consul Enterprise version 1.7.0 up to 1.8.4 includes a namespace replication bug which can be triggered to cause denial of service via infinite Raft writes. Fixed in 1.7.9 and 1.8.5.
HashiCorp Consul>=1.7.0<=1.8.4
go/github.com/hashicorp/consul>=1.8.0<1.8.5
go/github.com/hashicorp/consul>=1.7.0<1.7.9
● CVE-2020-12758
HashiCorp Consul and Consul Enterprise could crash when configured with an abnormally-formed service-router entry. Introduced in 1.6.0, fixed in 1.6.6 and 1.7.4. ### Specific Go Packages Affected gith...
HashiCorp Consul>=1.6.0<1.6.6
HashiCorp Consul>=1.6.0<1.6.6
● CVE-2020-12797
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. ### Specific...
go/github.com/hashicorp/consul>=1.7.0<1.7.4
go/github.com/hashicorp/consul>=1.6.0<1.6.6
HashiCorp Consul>=1.4.0<1.6.6
HashiCorp Consul>=1.4.0<=1.6.6
HashiCorp Consul>=1.7.0<1.7.4
HashiCorp Consul>=1.7.0<1.7.4
● CVE-2020-13170
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...
HashiCorp Consul>=1.4.0<1.6.6
HashiCorp Consul>=1.4.0<1.6.6
HashiCorp Consul>=1.7.0<1.7.4
HashiCorp Consul>=1.7.0<1.7.4
● CVE-2020-13250
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. ### Specific Go Packages Affec...
HashiCorp Consul>=1.2.0<1.6.6
HashiCorp Consul>=1.2.0<1.6.6
HashiCorp Consul>=1.7.0<1.7.4
HashiCorp Consul>=1.7.0<1.7.4
● CVE-2020-7219
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. ### Specific Go Packa...
HashiCorp Consul<1.6.2
HashiCorp Consul<1.6.2
● CVE-2020-7955
HashiCorp Consul>=1.4.1<1.6.2
HashiCorp Consul>=1.4.1<1.6.2
● CVE-2019-12291
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 defa...
HashiCorp Consul>=1.4.0<=1.5.0
go/github.com/hashicorp/consul>=1.4.0<1.5.1
● CVE-2019-9764
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 actu...
HashiCorp Consul=1.4.3
● CVE-2019-8336
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, ...
go/github.com/hashicorp/consul>=1.4.0<1.4.3
HashiCorp Consul>=1.4.0<1.4.3
HashiCorp Consul>=1.4.0<1.4.3
● CVE-2018-19653
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 step...
HashiCorp Consul>=0.5.1<=1.4.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2024 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203