Security readout for executives and security teams
Plain-English summary
Some Envoy versions could make the wrong access-control decision when a URL contained a fragment marker. If Envoy protected sensitive paths using RBAC or similar path rules, a crafted request could bypass the intended match and reach backend services. The business concern is unauthorized access to protected routes, not service outage.
Executive priority
Treat as high priority for Envoy deployments that enforce access to administrative or sensitive paths. Patch exposed or untrusted-traffic proxies first, then validate internal service mesh deployments that use path-based authorization.
Technical view
Envoy mishandled URI fragments by evaluating the fragment as part of the path or encoded path. Path-based authorization rules expecting a final sensitive element could mismatch, causing privilege escalation. Fixed versions remove fragments from incoming request URI paths: 1.19.1, 1.18.4, 1.17.4, and 1.16.5.
Likely exposure
Exposure is most likely where Envoy is internet-facing or accepts untrusted client traffic and uses RBAC or similar path-based authorization for sensitive routes. Systems not using vulnerable Envoy versions or not relying on path authorization for protected routes are less likely exposed.
Exploitation context
The source bundle does not show active exploitation, and KEV is false. Exploitation requires an affected Envoy version, untrusted request input, and path-based authorization rules that can be confused by a URI fragment.
Researcher notes
Affected ranges are 1.19.0 before 1.19.1, 1.18.0 before 1.18.4, 1.17.0 before 1.17.4, and 1.16.0 before 1.16.5. The weakness maps to authorization bypass behavior involving incorrect URI fragment handling.
Mitigation direction
- Upgrade Envoy to 1.19.1, 1.18.4, 1.17.4, 1.16.5, or later.
- Prioritize systems using Envoy RBAC or path-based authorization on sensitive routes.
- Review Envoy advisory and version history for branch-specific upgrade guidance.
- Avoid relying on configuration-only assumptions until vendor-fixed versions are deployed.
Validation and detection
- Inventory Envoy versions across gateways, sidecars, ingress, and edge proxy deployments.
- Identify RBAC or similar rules matching sensitive paths by final path element.
- Confirm deployed Envoy builds include the fragment-removal fix.
- Review proxy logs for unusual fragment-bearing requests to protected routes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-551: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2021-32779 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N3.94Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.6HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.envoyproxy.io/docs/envoy/v1.19.0/version_history/version_historyCVE reference · x_refsource_MISC
- https://github.com/envoyproxy/envoy/security/advisories/GHSA-r222-74fw-jqr9CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Behavior Order: Authorization Before Parsing and Canonicalization
Incorrect Behavior Order: Authorization Before Parsing and Canonicalization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.