Emissary Ingress
Approved changes feed: RSS · Atom
cpe:2.3:a:getambassador:emissary-ingress:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Getambassador (4ef8b4a1-5e53-5db1-813d-cf6319b61e37) |
|---|---|
| Product | Emissary Ingress (4100105c-0734-59fc-b9bd-fa193caf454b) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from purl2cpe mapping
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/emissary-ingress/emissary |
purl2cpe | 2026-06-01 10:16:13.714039 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2021-36371 |
vulnerable | 2026-06-08 05:32:52.097009 |
Details available
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.)
Published: 2021-07-09T20:19:45.000Z
Updated: 2024-08-04T00:54:51.414Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.