Описание
Traefik versions 3.7.0 through 3.7.6 contain a namespace confusion vulnerability in the Kubernetes Gateway API provider. When resolving HTTPRoute.spec.rules[].backendRefs[].filters[].extensionRef, Traefik used the backend Service namespace instead of the HTTPRoute namespace. A low-privileged route author holding a ReferenceGrant for a cross-namespace Service could therefore bind a Traefik Middleware from the backend namespace without a separate grant for that middleware, potentially injecting trusted reverse-proxy identity headers into downstream requests. The issue is fixed in version 3.7.7.
A flaw was found in Traefik, a cloud-native edge router. A low-privileged user in a Kubernetes environment could exploit a namespace confusion vulnerability within the Kubernetes Gateway API provider. This flaw allows an attacker to bypass security controls by incorrectly binding a Traefik Middleware from a different namespace, potentially leading to the injection of trusted identity headers into network requests. This could result in unauthorized access or privilege escalation within the Kubernetes cluster.
Отчет
This is an Important flaw in Traefik's Kubernetes Gateway API provider, affecting Red Hat OpenShift Dev Spaces. A low-privileged user in a Kubernetes environment can exploit a namespace confusion vulnerability to bypass security controls. This allows for the incorrect binding of a Traefik Middleware from a different namespace, potentially leading to the injection of trusted identity headers and subsequent privilege escalation within the cluster.
Затронутые пакеты
| Платформа | Пакет | Состояние | Рекомендация | Релиз |
|---|---|---|---|---|
| Red Hat OpenShift Dev Spaces | devspaces/traefik-rhel9 | Affected |
Показывать по
Ссылки на источники
Дополнительная информация
Статус:
9.6 Critical
CVSS3
Связанные уязвимости
Traefik versions 3.7.0 through 3.7.6 contain a namespace confusion vulnerability in the Kubernetes Gateway API provider. When resolving HTTPRoute.spec.rules[].backendRefs[].filters[].extensionRef, Traefik used the backend Service namespace instead of the HTTPRoute namespace. A low-privileged route author holding a ReferenceGrant for a cross-namespace Service could therefore bind a Traefik Middleware from the backend namespace without a separate grant for that middleware, potentially injecting trusted reverse-proxy identity headers into downstream requests. The issue is fixed in version 3.7.7.
Traefik versions 3.7.0 through 3.7.6 contain a namespace confusion vul ...
Traefik versions 3.7.0 through 3.7.6 contain a namespace confusion vulnerability in the Kubernetes Gateway API provider. When resolving HTTPRoute.spec.rules[].backendRefs[].filters[].extensionRef, Traefik used the backend Service namespace instead of the HTTPRoute namespace. A low-privileged route author holding a ReferenceGrant for a cross-namespace Service could therefore bind a Traefik Middleware from the backend namespace without a separate grant for that middleware, potentially injecting trusted reverse-proxy identity headers into downstream requests. The issue is fixed in version 3.7.7.
9.6 Critical
CVSS3