CVE-2021-32777: 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-32777
- 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 when ext-authz extension is sending request headers to the external authorization service it must merge multiple value headers according to the HTTP spec. However, only the last header value is sent. This may allow specifically crafted requests to bypass authorization. Attackers may be able to escalate privileges when using ext-authz extension or back end service that uses multiple value headers for authorization. A specifically constructed request may be delivered by an untrusted downstream peer in the presence of ext-authz extension. Envoy versions 1.19.1, 1.18.4, 1.17.4, 1.16.5 contain fixes to the ext-authz extension to correctly merge multiple request header values, when sending request for authorization.
References
- CVE-2021-32777 on the NVD
- Advisory: https://nvd.nist.gov/vuln/detail/CVE-2021-32777
- Web: https://github.com/envoyproxy/envoy/security/advisories/GHSA-6g4j-5vrw-2m8h
- Web: https://www.envoyproxy.io/docs/envoy/v1.19.0/version_history/version_history
- Web: https://github.com/envoyproxy/envoy/security/advisories/GHSA-6g4j-5vrw-2m8h
- 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.