- Veröffentlicht
- 24.08.2021 21:00
- Zuletzt geändert
- 08.09.2026
- EPSS (30 Tage)
- 1.0 %
- CVSS-Vektor
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Beschreibung
Originaltext der Quelle, nicht übersetzt.
Envoy is an open source L7 proxy and communication bus designed for large modern service oriented architectures. In affected versions envoy incorrectly handled a URI '#fragment' element as part of the path element. Envoy is configured with an RBAC filter for authorization or similar mechanism with an explicit case of a final "/admin" path element, or is using a negative assertion with final path element of "/admin". The client sends request to "/app1/admin#foo". In Envoy prior to 1.18.0, or 1.18.0+ configured with path_normalization=false. Envoy treats fragment as a suffix of the query string when present, or as a suffix of the path when query string is absent, so it evaluates the final path element as "/admin#foo" and mismatches with the configured "/admin" path element. In Envoy 1.18.0+ configured with path_normalization=true. Envoy transforms this to /app1/admin%23foo and mismatches with the configured /admin prefix. The resulting URI is sent to the next server-agent with the offending "#foo" fragment which violates RFC3986 or with the nonsensical "%23foo" text appended. A specifically constructed request with URI containing '#fragment' element delivered by an untrusted client in the presence of path based request authorization resulting in escalation of Privileges when path based request authorization extensions. Envoy versions 1.19.1, 1.18.4, 1.17.4, 1.16.5 contain fixes that removes fragment from URI path in incoming requests.
Status beim Hersteller
Red Hat stuft seine Produktlinien ein: 2 behoben, 2 nicht betroffen.
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.17-3.el8RHSA-2021:3273 (über RHSA-2021:3273)
Red Hat:service_mesh:1.1::el8servicemesh-citadel0:1.1.17-3.el8RHSA-2021:3273 (über RHSA-2021:3273)
Red Hat:service_mesh:1.1::el8servicemesh-galley0:1.1.17-3.el8RHSA-2021:3273 (über RHSA-2021:3273)
Red Hat:service_mesh:1.1::el8servicemesh-istioctl0:1.1.17-3.el8RHSA-2021:3273 (über RHSA-2021:3273)
Red Hat:service_mesh:1.1::el8servicemesh-mixc0:1.1.17-3.el8RHSA-2021:3273 (über RHSA-2021:3273)
Red Hat:service_mesh:1.1::el8servicemesh-mixs0:1.1.17-3.el8RHSA-2021:3273 (über RHSA-2021:3273)
Red Hat:service_mesh:1.1::el8servicemesh-pilot-agent0:1.1.17-3.el8RHSA-2021:3273 (über RHSA-2021:3273)
Red Hat:service_mesh:1.1::el8servicemesh-pilot-discovery0:1.1.17-3.el8RHSA-2021:3273 (über RHSA-2021:3273)
Red Hat:service_mesh:1.1::el8servicemesh-proxy0:1.1.17-2.el8CVE-2021-32779
Red Hat:service_mesh:1.1::el8servicemesh-proxy0:1.1.17-2.el8RHSA-2021:3273 (über RHSA-2021:3273)
Red Hat:service_mesh:1.1::el8servicemesh-sidecar-injector0:1.1.17-3.el8RHSA-2021:3273 (über RHSA-2021:3273)
Red Hat:service_mesh:2.0::el8servicemesh0:2.0.7-3.el8RHSA-2021:3272 (über RHSA-2021:3272)
Red Hat:service_mesh:2.0::el8servicemesh-istioctl0:2.0.7-3.el8RHSA-2021:3272 (über RHSA-2021:3272)
Red Hat:service_mesh:2.0::el8servicemesh-mixc0:2.0.7-3.el8RHSA-2021:3272 (über RHSA-2021:3272)
Red Hat:service_mesh:2.0::el8servicemesh-mixs0:2.0.7-3.el8RHSA-2021:3272 (über RHSA-2021:3272)
Red Hat:service_mesh:2.0::el8servicemesh-pilot-agent0:2.0.7-3.el8RHSA-2021:3272 (über RHSA-2021:3272)
Red Hat:service_mesh:2.0::el8servicemesh-pilot-discovery0:2.0.7-3.el8RHSA-2021:3272 (über RHSA-2021:3272)
Red Hat:service_mesh:2.0::el8servicemesh-proxy0:2.0.7-3.el8CVE-2021-32779
Red Hat:service_mesh:2.0::el8servicemesh-proxy0:2.0.7-3.el8RHSA-2021:3272 (über RHSA-2021:3272)
Weitere betroffene Pakete (3)
Bitnamienvoy1.16.0 → 1.16.5, 1.17.0 → 1.17.4, 1.18.0 → 1.18.4, 1.19.0 → 1.19.1BIT-envoy-2021-32779
CVEenvoyproxy/envoykein Fix bekanntCVE-2021-32779
NVDenvoyproxy:envoy1.16.0 → 1.16.5, 1.17.0 → 1.17.4, 1.18.0 → 1.18.4CVE-2021-32779
Empfohlene Prüfung
- Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
- Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
- 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.
Referenzen
- www.envoyproxy.io/docs/envoy/v1.19.0/version_history/version_history
- github.com/envoyproxy/envoy/security/advisories/GHSA-r222-74fw-jqr9
- nvd.nist.gov/vuln/detail/CVE-2021-32779
- security.access.redhat.com/data/csaf/v2/vex/2021/cve-2021-32779.json
- access.redhat.com/security/cve/CVE-2021-32779
- bugzilla.redhat.com/show_bug.cgi
- www.cve.org/CVERecord
- istio.io/latest/news/security/istio-security-2021-008/