-
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-2022-29226 #486
Labels
excluded: NOT_GO_CODE
This vulnerability does not refer to a Go module.
Comments
neild
added
excluded: NOT_GO_CODE
This vulnerability does not refer to a Go module.
and removed
NotGoVuln
labels
Aug 10, 2022
This was referenced Apr 4, 2023
This was referenced Jul 13, 2023
This was referenced Jul 25, 2023
This was referenced Nov 8, 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-2022-29226 references github.com/envoyproxy/envoy, which may be a Go module.
Description:
Envoy is a cloud-native high-performance proxy. In versions prior to 1.22.1 the OAuth filter implementation does not include a mechanism for validating access tokens, so by design when the HMAC signed cookie is missing a full authentication flow should be triggered. However, the current implementation assumes that access tokens are always validated thus allowing access in the presence of any access token attached to the request. Users are advised to upgrade. There is no known workaround for this issue.
Links:
See doc/triage.md for instructions on how to triage this report.
The text was updated successfully, but these errors were encountered: