CVE-2021-32779

highPriorität · verfolgen · 33OT-Risiko · erhöhtEPSS 0.009 · 61. PerzentilEUUS
grimoire priorityP2 · Scheduled
Exploitable?
—
no known exploitation
Likely / severe?
0.95% (61st) EPSS
CVSS 7.5 · high
Is it mine?
67 products
Prüfe deine Angriffsfläche
Who says so?
5 sources
cnnvd · enisa_euvd · osv · nvd

EPSS · bewertet 2026-10-27

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.

01

Behebungen

Hersteller-Fix, Mitigation oder Workaround, wie von den Quellen veröffentlicht.

Ein Hersteller-Fix ist verfügbar.

  • Behobenservicemesh-proxy-0:2.0.7-3.el8.ppc64le as a component of OpenShift Service Mesh 2.0redhat_csaf

    The OpenShift Service Mesh Release Notes provide information on the features and known issues: https://docs.openshift.com/container-platform/latest/service_mesh/v2x/servicemesh-release-notes.html

    https://access.redhat.com/errata/RHSA-2021:3272
  • Behobenservicemesh-proxy-0:2.0.7-3.el8.s390x as a component of OpenShift Service Mesh 2.0redhat_csaf

    The OpenShift Service Mesh Release Notes provide information on the features and known issues: https://docs.openshift.com/container-platform/latest/service_mesh/v2x/servicemesh-release-notes.html

    https://access.redhat.com/errata/RHSA-2021:3272
  • Behobenservicemesh-proxy-0:2.0.7-3.el8.src as a component of OpenShift Service Mesh 2.0redhat_csaf

    The OpenShift Service Mesh Release Notes provide information on the features and known issues: https://docs.openshift.com/container-platform/latest/service_mesh/v2x/servicemesh-release-notes.html

    https://access.redhat.com/errata/RHSA-2021:3272
  • Behobenservicemesh-proxy-0:2.0.7-3.el8.x86_64 as a component of OpenShift Service Mesh 2.0redhat_csaf

    The OpenShift Service Mesh Release Notes provide information on the features and known issues: https://docs.openshift.com/container-platform/latest/service_mesh/v2x/servicemesh-release-notes.html

    https://access.redhat.com/errata/RHSA-2021:3272
  • Behobenservicemesh-proxy-0:1.1.17-2.el8.ppc64le as a component of OpenShift Service Mesh 1.1redhat_csaf

    The OpenShift Service Mesh Release Notes provide information on the features and known issues: https://docs.openshift.com/container-platform/4.8/service_mesh/v1x/servicemesh-release-notes.html

    https://access.redhat.com/errata/RHSA-2021:3273
  • Behobenservicemesh-proxy-0:1.1.17-2.el8.s390x as a component of OpenShift Service Mesh 1.1redhat_csaf

    The OpenShift Service Mesh Release Notes provide information on the features and known issues: https://docs.openshift.com/container-platform/4.8/service_mesh/v1x/servicemesh-release-notes.html

    https://access.redhat.com/errata/RHSA-2021:3273
  • Behobenservicemesh-proxy-0:1.1.17-2.el8.src as a component of OpenShift Service Mesh 1.1redhat_csaf

    The OpenShift Service Mesh Release Notes provide information on the features and known issues: https://docs.openshift.com/container-platform/4.8/service_mesh/v1x/servicemesh-release-notes.html

    https://access.redhat.com/errata/RHSA-2021:3273
  • Behobenservicemesh-proxy-0:1.1.17-2.el8.x86_64 as a component of OpenShift Service Mesh 1.1redhat_csaf

    The OpenShift Service Mesh Release Notes provide information on the features and known issues: https://docs.openshift.com/container-platform/4.8/service_mesh/v1x/servicemesh-release-notes.html

    https://access.redhat.com/errata/RHSA-2021:3273
02

cvss

Technischer Schweregrad, 0–10. Eine Zeile je Quelle.

8.6
010

Basiswert 0–10 · höher = schwerwiegender · Vektor überfahren zum Auflösen

v2.07.5highAV:N/AC:L/Au:N/C:P/I:P/A:Pprimary · NVD / NIST USAusnutzbarkeit 10 · Auswirkung 6.4
v3.18.3highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:Lprimary · NVD / NIST USAusnutzbarkeit 3.9 · Auswirkung 3.7
v3.18.6highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:Nsecondary · ENISA EU
v3.18.6highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:Nsecondary · security-advisories@github.comAusnutzbarkeit 3.9 · Auswirkung 4
v3.17.6highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L/E:Usecondary · CVSS-BT (t0sche)
v3.18.3highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:Lsecondary · Red Hat Product Security US
03

schwächen

Die CWE-Schwächeklassen, zu denen dies gehört.

04

betroffene Produkte (67)

Betroffene Produkte und Versionsbereiche.

20 von 67 angezeigt
05

Advisories (3)

Hersteller- und Ökosystem-Meldungen dazu.

  • RHSA-2021:3272Red Hat Security Advisory: Red Hat OpenShift Service Mesh 2.0.7.1 security update2021-08-25csaf · redhat_csafUS

    An update for servicemesh and servicemesh-proxy is now available for OpenShift Service Mesh 2.0. Red Hat Product Security has rated this update as having a security impact of Important. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

  • RHSA-2021:3273Red Hat Security Advisory: Red Hat OpenShift Service Mesh 1.1.17.1 security update2021-08-25csaf · redhat_csafUS

    An update for servicemesh and servicemesh-proxy is now available for OpenShift Service Mesh 1.1. Red Hat Product Security has rated this update as having a security impact of Important. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

  • BIT-envoy-2021-32779Incorrectly handling of URI '#fragment' element as part of the path element2024-03-06vendor · osvUS

    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.

06

auch bekannt als (3)

Weitere Namen und Kennungen dieser Entität.

07

quellen

Welche Quellen diesen Datensatz belegen und wann.

veröffentlicht 2021-08-24geändert 2026-06-17
09

Referenzen (9)

Externe Belege — Patches, Meldungen, Analysen.

scry

Angreifer nutzen Schwachstellen wie diese gegen im Internet exponierte Dienste aus. Sehen Sie mit einem kostenlosen Passiv-Scan, was exponiert ist.

Kostenloser Scan