← Übersicht Red Hat Enterprise Linux

Bypass of path matching rules using escaped slash characters

CVE-2021-29492 · BIT-envoy-2021-29492 · GHSA-4987-27fx-x6cf

Hoch · CVSS 8.3 Red Hat: Important Netzwerk · ohne Login Fix verfügbar

Veröffentlicht
11.05.2021 21:00
Zuletzt geändert
08.09.2026
EPSS (30 Tage)
63.1 %
CVSS-Vektor
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L

Beschreibung

Originaltext der Quelle, nicht übersetzt.

Envoy is a cloud-native edge/middle/service proxy. Envoy does not decode escaped slash sequences `%2F` and `%5C` in HTTP URL paths in versions 1.18.2 and before. A remote attacker may craft a path with escaped slashes, e.g. `/something%2F..%2Fadmin`, to bypass access control, e.g. a block on `/admin`. A backend server could then decode slash sequences and normalize path and provide an attacker access beyond the scope provided for by the access control policy. ### Impact Escalation of Privileges when using RBAC or JWT filters with enforcement based on URL path. Users with back end servers that interpret `%2F` and `/` and `%5C` and `\` interchangeably are impacted. ### Attack Vector URL paths containing escaped slash characters delivered by untrusted client. Patches in versions 1.18.3, 1.17.3, 1.16.4, 1.15.5 contain new path normalization option to decode escaped slash characters. As a workaround, if back end servers treat `%2F` and `/` and `%5C` and `\` interchangeably and a URL path based access control is configured, one may reconfigure the back end server to not treat `%2F` and `/` and `%5C` and `\` interchangeably.

Status beim Hersteller

Red Hat stuft seine Produktlinien ein: 2 behoben, 2 nicht betroffen.

OpenShift Service Mesh 1.1 Behoben servicemesh-proxy-1.1.14-1.el8 RHSA-2021:1540
OpenShift Service Mesh 2.0 Behoben servicemesh-operator-2.0.4-3.el8, servicemesh-proxy-2.0.4-1.el8 RHSA-2021:1538
Nicht betroffen (2)
OpenShift Service Mesh 1.1Nicht betroffenverwundbarer Code nicht enthaltenservicemesh
OpenShift Service Mesh 2.0Nicht betroffenverwundbarer Code nicht enthaltenservicemesh

Betroffene Pakete im beobachteten Stack

Red Hat:service_mesh:1.1::el8servicemesh0:1.1.14-1.el8RHSA-2021:1540 (über RHSA-2021:1540)
Red Hat:service_mesh:1.1::el8servicemesh-citadel0:1.1.14-1.el8RHSA-2021:1540 (über RHSA-2021:1540)
Red Hat:service_mesh:1.1::el8servicemesh-galley0:1.1.14-1.el8RHSA-2021:1540 (über RHSA-2021:1540)
Red Hat:service_mesh:1.1::el8servicemesh-istioctl0:1.1.14-1.el8RHSA-2021:1540 (über RHSA-2021:1540)
Red Hat:service_mesh:1.1::el8servicemesh-mixc0:1.1.14-1.el8RHSA-2021:1540 (über RHSA-2021:1540)
Red Hat:service_mesh:1.1::el8servicemesh-mixs0:1.1.14-1.el8RHSA-2021:1540 (über RHSA-2021:1540)
Red Hat:service_mesh:1.1::el8servicemesh-pilot-agent0:1.1.14-1.el8RHSA-2021:1540 (über RHSA-2021:1540)
Red Hat:service_mesh:1.1::el8servicemesh-pilot-discovery0:1.1.14-1.el8RHSA-2021:1540 (über RHSA-2021:1540)
Red Hat:service_mesh:1.1::el8servicemesh-proxy0:1.1.14-1.el8CVE-2021-29492
Red Hat:service_mesh:1.1::el8servicemesh-proxy0:1.1.14-1.el8RHSA-2021:1540 (über RHSA-2021:1540)
Red Hat:service_mesh:1.1::el8servicemesh-sidecar-injector0:1.1.14-1.el8RHSA-2021:1540 (über RHSA-2021:1540)
Red Hat:service_mesh:2.0::el8servicemesh0:2.0.4-1.el8RHSA-2021:1538 (über RHSA-2021:1538)
Red Hat:service_mesh:2.0::el8servicemesh-istioctl0:2.0.4-1.el8RHSA-2021:1538 (über RHSA-2021:1538)
Red Hat:service_mesh:2.0::el8servicemesh-mixc0:2.0.4-1.el8RHSA-2021:1538 (über RHSA-2021:1538)
Red Hat:service_mesh:2.0::el8servicemesh-mixs0:2.0.4-1.el8RHSA-2021:1538 (über RHSA-2021:1538)
Red Hat:service_mesh:2.0::el8servicemesh-operator0:2.0.4-3.el8CVE-2021-29492
Red Hat:service_mesh:2.0::el8servicemesh-operator0:2.0.4-3.el8RHSA-2021:1538 (über RHSA-2021:1538)
Red Hat:service_mesh:2.0::el8servicemesh-pilot-agent0:2.0.4-1.el8RHSA-2021:1538 (über RHSA-2021:1538)
Red Hat:service_mesh:2.0::el8servicemesh-pilot-discovery0:2.0.4-1.el8RHSA-2021:1538 (über RHSA-2021:1538)
Red Hat:service_mesh:2.0::el8servicemesh-proxy0:2.0.4-1.el8CVE-2021-29492
Red Hat:service_mesh:2.0::el8servicemesh-proxy0:2.0.4-1.el8RHSA-2021:1538 (über RHSA-2021:1538)
Weitere betroffene Pakete (3)
Bitnamienvoy1.15.5, 1.16.0 → 1.16.4, 1.17.0 → 1.17.3, 1.18.0 → 1.18.3BIT-envoy-2021-29492
CVEenvoyproxy/envoykein Fix bekanntCVE-2021-29492
NVDenvoyproxy:envoy1.15.5, 1.16.0 → 1.16.4, 1.17.0 → 1.17.3, 1.18.0 → 1.18.3CVE-2021-29492

Empfohlene Prüfung

  1. Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
  2. Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
  3. Erreichbarkeit beachten: Der Angriffsweg (Netzwerk · ohne Login) ist aus dem CVSS-Vektor abgeleitet.

Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.