User Impersonation Affecting envoyproxy/envoy package, versions [,1.12.6)[1.13.0,1.13.4)[1.14.0,1.14.4)


Severity

Recommended
0.0
medium
0
10

CVSS assessment made by Snyk's Security Team. Learn more

Threat Intelligence

EPSS
0.05% (22nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-UNMANAGED-ENVOYPROXYENVOY-2365524
  • published26 Jan 2022
  • disclosed14 Jul 2020
  • creditUnknown

Introduced: 14 Jul 2020

CVE-2020-15104  (opens in a new tab)
CWE-346  (opens in a new tab)

How to fix?

Upgrade envoyproxy/envoy to version 1.12.6, 1.13.4, 1.14.4 or higher.

Overview

Affected versions of this package are vulnerable to User Impersonation. In Envoy before versions 1.12.6, 1.13.4, 1.14.4, and 1.15.0 when validating TLS certificates, Envoy would incorrectly allow a wildcard DNS Subject Alternative Name apply to multiple subdomains. For example, with a SAN of *.example.com, Envoy would incorrectly allow nested.subdomain.example.com, when it should only allow subdomain.example.com. This defect applies to both validating a client TLS certificate in mTLS, and validating a server TLS certificate for upstream connections. This vulnerability is only applicable to situations where an untrusted entity can obtain a signed wildcard TLS certificate for a domain of which you only intend to trust a subdomain of. For example, if you intend to trust api.mysubdomain.example.com, and an untrusted actor can obtain a signed TLS certificate for *.example.com or *.com. Configurations are vulnerable if they use verify_subject_alt_name in any Envoy version, or if they use match_subject_alt_names in version 1.14 or later. This issue has been fixed in Envoy versions 1.12.6, 1.13.4, 1.14.4, 1.15.0.

References

CVSS Scores

version 3.1