CVE-2021-36371

Emissary-Ingress (formerly Ambassador API Gateway) through 1.13.9 allows attackers to bypass client certificate requirements (i.e., mTLS cert_required) on backend upstreams when more than one TLSContext is defined and at least one configuration exists that does not require client certificate authentication. The attacker must send an SNI specifying an unprotected backend and an HTTP Host header specifying a protected backend. (2.x versions are unaffected. 1.x versions are unaffected with certain configuration settings involving prune_unreachable_routes and a wildcard Host resource.)
Configurations

Configuration 1 (hide)

cpe:2.3:a:getambassador:emissary-ingress:*:*:*:*:*:*:*:*

History

21 Nov 2024, 06:13

Type Values Removed Values Added
References () https://github.com/emissary-ingress/emissary/issues/3340 - Exploit, Third Party Advisory () https://github.com/emissary-ingress/emissary/issues/3340 - Exploit, Third Party Advisory
References () https://github.com/emissary-ingress/emissary/releases/tag/v2.0.0-ea - Release Notes, Third Party Advisory () https://github.com/emissary-ingress/emissary/releases/tag/v2.0.0-ea - Release Notes, Third Party Advisory

Information

Published : 2021-07-09 21:15

Updated : 2024-11-21 06:13


NVD link : CVE-2021-36371

Mitre link : CVE-2021-36371

CVE.ORG link : CVE-2021-36371


JSON object : View

Products Affected

getambassador

  • emissary-ingress
CWE
CWE-295

Improper Certificate Validation