-
Notifications
You must be signed in to change notification settings - Fork 82
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
CVE-2020-26160 - github.com/dgrijalva/jwt-go #150
Comments
(v6 - #18) move all remaining core stuff into core, clean up tests, move Relay app starter to main package
We've released v6.4.1 which should fix this. |
Thanks. i will leave it to you to close the issue. FWIW, for folks using the ld-relay library, we will still need to add the
|
I will leave a pointer to the indirect dependency issues:
Once the above are resolved, we can remove the |
@asaha-atlassian:
Yes, that's why we added this section to the relevant docs: https://github.com/launchdarkly/ld-relay/blob/v6/docs/in-app.md#additional-notes |
Describe the bug
Currently
ld-relay
pulls in dgrijalva/jwt-go via the following path:There is an existing CVE against the package version that's currently used (v3.2.0).
To reproduce
github.com/dgrijalva/jwt-go v3.2.0+incompatible/go.mod h1:E3ru+11k8xSBh+hMPgOLZmtrrCbhqsmaPHjLKYnJCaQ=
Fix
The above package now is under a new ownership at golang-jwt/jwt. The latest release contains the fix. The migration guide suggests the following:
Since this is not a direct dependency, for now perhaps we could do the above in ld-relay's go.mod file.
The text was updated successfully, but these errors were encountered: