CVE-2021-32779
highpriority · track · 33OT risk · elevatedEPSS 0.009 · 61 %ileEUUSEPSS · scored 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.
remediations
Vendor fix, mitigation, or workaround guidance, as published by each source.
A vendor fix is available.
- Fixedservicemesh-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 - Fixedservicemesh-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 - Fixedservicemesh-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 - Fixedservicemesh-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 - Fixedservicemesh-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 - Fixedservicemesh-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 - Fixedservicemesh-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 - Fixedservicemesh-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
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (67)
Products and version ranges known to be affected.
- servicemesh-0:1.1.17-3.el8.ppc64le as a component of OpenShift Service Mesh 1.1all versionsnot affectedredhat_csafUS
- servicemesh-0:1.1.17-3.el8.s390x as a component of OpenShift Service Mesh 1.1all versionsnot affectedredhat_csafUS
- servicemesh-0:1.1.17-3.el8.src as a component of OpenShift Service Mesh 1.1all versionsnot affectedredhat_csafUS
- servicemesh-0:1.1.17-3.el8.x86_64 as a component of OpenShift Service Mesh 1.1all versionsnot affectedredhat_csafUS
- servicemesh-0:2.0.7-3.el8.ppc64le as a component of OpenShift Service Mesh 2.0all versionsnot affectedredhat_csafUS
- servicemesh-0:2.0.7-3.el8.s390x as a component of OpenShift Service Mesh 2.0all versionsnot affectedredhat_csafUS
- servicemesh-0:2.0.7-3.el8.src as a component of OpenShift Service Mesh 2.0all versionsnot affectedredhat_csafUS
- servicemesh-0:2.0.7-3.el8.x86_64 as a component of OpenShift Service Mesh 2.0all versionsnot affectedredhat_csafUS
advisories (3)
Vendor and ecosystem advisories describing this.
- 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.
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (9)
External citations — patches, advisories, analysis.
- https://access.redhat.com/security/cve/cve-2021-32779cnnvd
- https://github.com/envoyproxy/envoy/security/advisories/GHSA-r222-74fw-jqr9cnnvd
- https://packetstormsecurity.com/files/163947/Red-Hat-Security-Advisory-2021-3273-01.htmlcnnvd
- https://www.auscert.org.au/bulletins/ESB-2021.2906cnnvd
- https://www.envoyproxy.io/docs/envoy/v1.19.0/version_history/version_historycnnvd
- https://github.com/envoyproxy/envoy/security/advisories/GHSA-r222-74fw-jqr9enisa_euvd
- https://www.envoyproxy.io/docs/envoy/v1.19.0/version_history/version_historyenisa_euvd
- https://github.com/envoyproxy/envoy/security/advisories/GHSA-r222-74fw-jqr9Third Party Advisorynvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan