-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x/vulndb: potential Go vuln in github.com/envoyproxy/envoy: CVE-2023-27487 #1690
Labels
excluded: NOT_GO_CODE
This vulnerability does not refer to a Go module.
Comments
tatianab
added
the
excluded: NOT_GO_CODE
This vulnerability does not refer to a Go module.
label
Apr 5, 2023
Change https://go.dev/cl/482615 mentions this issue: |
This was referenced Jul 13, 2023
This was referenced Jul 25, 2023
This was referenced Nov 8, 2023
This was referenced Feb 10, 2024
This was referenced Apr 10, 2024
This was referenced Jun 7, 2024
This was referenced Sep 20, 2024
This was referenced Dec 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
CVE-2023-27487 references github.com/envoyproxy/envoy, which may be a Go module.
Description:
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 forjwt_authn
checks if thejwt_authn
filter is used, and any other upstream use of the x-envoy-original-path header. Attackers may forge a trustedx-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:
Cross references:
See doc/triage.md for instructions on how to triage this report.
The text was updated successfully, but these errors were encountered: