Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2021-32779

envoyproxy/envoy: HTTP request with a URL fragment in the URI can bypass authorization policies

Overview

Published
24 Aug 2021
Modified
17 Jun 2026
High CVE
1 Registry packages
26 OS packages
2 Linux distributions
Yes Fix available

Description

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.

Source: OX vulnerability database

Severity

8.3 · HIGH

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L

Weakness: CWE-551, CWE-863, CWE-697

Affected packages · 1

Packages affected by CVE-2021-32779
EcosystemPackageVulnerableFixed in
Bitnami envoy >=1.16.0, <1.16.5>=1.17.0, <1.17.4>=1.18.0, <1.18.4>=1.19.0, <1.19.1 1.16.51.17.41.18.41.19.1

Open a package to see all its vulnerabilities.

Operating systems · 10 fixes

Oracle Linux 2 releases · 4 packages

fixed 7
istio kubeadm olcne-agent istio-pilot-agent
Oracle Linux fixes for CVE-2021-32779
ReleasePackageFixed in
7 istio +1 1.10.4-3.el7
7 kubeadm +2 1.20.11-4.el7
7 olcne-agent +8 1.3.2-2.el7
8 istio +1 1.10.4-3.el8
8 kubeadm +2 1.20.11-4.el8
8 olcne-agent +8 1.3.2-2.el8

1 more row

Red Hat 1 release · 2 packages

fixed 3
servicemesh-proxy servicemesh
Red Hat fixes for CVE-2021-32779
ReleasePackageFixed inAdvisory
8 servicemesh-proxy 0:1.1.17-2.el8 RHSA-2021:3273
8 servicemesh +8 0:1.1.17-3.el8 RHSA-2021:3273
8 servicemesh +6 0:2.0.7-3.el8 RHSA-2021:3272

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.