Description

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, and 1.10.1.

Related CPE's

a

hashicorp

consul

6

References

https://discuss.hashicorp.com/t/hcsec-2021-17-consul-s-envoy-tls-configuration-did-not-validate-destination-service-subject-alternative-names/26856

Vendor Advisory

https://github.com/hashicorp/consul/releases/tag/v1.10.1

Third Party Advisory

https://security.gentoo.org/glsa/202208-09

Third Party Advisory

https://www.hashicorp.com/blog/category/consul

Vendor Advisory

https://discuss.hashicorp.com/t/hcsec-2021-17-consul-s-envoy-tls-configuration-did-not-validate-destination-service-subject-alternative-names/26856

Vendor Advisory

https://github.com/hashicorp/consul/releases/tag/v1.10.1

Third Party Advisory

https://security.gentoo.org/glsa/202208-09

Third Party Advisory

https://www.hashicorp.com/blog/category/consul

Vendor Advisory

Weaknesses

[email protected]

Primary
CWE-295

CVSS impact metrics

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

7.5 · High

Information

Source identifier

[email protected]

Vulnerability status

Modified

Published

2021-07-17T16:15:07.723Z

4 years ago

Last modified

2024-11-21T05:07:18.077Z

1 year ago