CVE-2021-32779: Envoy is an open source L7 proxy and communication bus designed for large modern service oriented architectures.
High CVSS 8.3
- CVE id
- CVE-2021-32779
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| Envoy Runtimes and servers |
>= 1.16.0, < 1.16.5 >= 1.17.0, < 1.17.4 >= 1.18.0, < 1.18.4 |
1.16.5, 1.17.4, 1.18.4 |
How to fix it
Upgrade Envoy to the fixed release of the line you run: 1.16.5, 1.17.4, 1.18.4.
envoy --version
- Upgrade Envoy (the envoyproxy/envoy image tag) to the patched release.
A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.
Details
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 pathnormalization=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 pathnormalization=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.
References
- CVE-2021-32779 on the NVD
- Advisory: https://nvd.nist.gov/vuln/detail/CVE-2021-32779
- Web: https://github.com/envoyproxy/envoy/security/advisories/GHSA-r222-74fw-jqr9
- Web: https://www.envoyproxy.io/docs/envoy/v1.19.0/version_history/version_history
- Web: https://github.com/envoyproxy/envoy/security/advisories/GHSA-r222-74fw-jqr9
- Web: https://www.envoyproxy.io/docs/envoy/v1.19.0/version_history/version_history
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.