CVE-2023-27487: Envoy is an open source edge and service proxy designed for cloud-native applications.
Critical CVSS 9.1
- CVE id
- CVE-2023-27487
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| Envoy Runtimes and servers |
< 1.22.9 >= 1.23.0, < 1.23.6 >= 1.24.0, < 1.24.4 >= 1.25.0, < 1.25.3 |
1.22.9, 1.23.6, 1.24.4, 1.25.3 |
How to fix it
Upgrade Envoy to the fixed release of the line you run: 1.22.9, 1.23.6, 1.24.4, 1.25.3.
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 edge and service proxy designed for cloud-native applications. Prior to versions 1.26.0, 1.25.3, 1.24.4, 1.23.6, and 1.22.9, the client may bypass JSON Web Token (JWT) checks and forge fake original paths. The header x-envoy-original-path should be an internal header, but Envoy does not remove this header from the request at the beginning of request processing when it is sent from an untrusted client. The faked header would then be used for trace logs and grpc logs, as well as used in the URL used for jwt_authn checks if the jwt_authn filter is used, and any other upstream use of the x-envoy-original-path header. Attackers may forge a trusted x-envoy-original-path header. Versions 1.26.0, 1.25.3, 1.24.4, 1.23.6, and 1.22.9 have patches for this issue.
References
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.