Envoy Gateway custom backendRef cross-namespace ReferenceGrant bypass
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| envoyproxy | gateway | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Envoyproxy | Gateway |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-fcrp-7gc2-93g7 | Envoy Gateway custom backendRef cross-namespace ReferenceGrant bypass |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.413% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Envoyproxy
Envoyproxy gateway |
|
| Vendors & Products |
Envoyproxy
Envoyproxy gateway |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Envoy Gateway is an open source project for managing Envoy Proxy as a standalone or Kubernetes-based application gateway. Prior to 1.7.4 and 1.8.1, an HTTPRoute can use an extension-managed custom backendRef to reference a backend resource in another namespace without a matching Gateway API ReferenceGrant in the target namespace. The custom-backend branch in internal/gatewayapi/route.go omits validateBackendNamespace, allowing the route-owning namespace to bind to and use the resource without the backend namespace owner's consent and violating the Gateway API cross-namespace authorization model. This issue is fixed in versions 1.7.4 and 1.8.1. | |
| Title | Envoy Gateway custom backendRef cross-namespace ReferenceGrant bypass | |
| Weaknesses | CWE-862 | |
| References |
|
|
| Metrics |
cvssV3_1
|