Skip to content
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

Closed
asaha123 opened this issue Jul 26, 2021 · 4 comments
Closed

CVE-2020-26160 - github.com/dgrijalva/jwt-go #150

asaha123 opened this issue Jul 26, 2021 · 4 comments

Comments

@asaha123
Copy link

Describe the bug

Currently ld-relay pulls in dgrijalva/jwt-go via the following path:

ldrelay -> prometheus exporter -> prometheus client -> prometheus common -> go-kit -> jwt-go

There is an existing CVE against the package version that's currently used (v3.2.0).

To reproduce

  • Inspect go.sum: 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:

$ go mod edit -replace github.com/dgrijalva/jwt-go=github.com/golang-jwt/jwt@v3.2.1+incompatible
$ go mod tidy

Since this is not a direct dependency, for now perhaps we could do the above in ld-relay's go.mod file.

LaunchDarklyReleaseBot pushed a commit that referenced this issue Jul 29, 2021
(v6 - #18) move all remaining core stuff into core, clean up tests, move Relay app starter to main package
@eli-darkly
Copy link
Contributor

We've released v6.4.1 which should fix this.

@asaha123
Copy link
Author

asaha123 commented Aug 2, 2021

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 replace directive TIL and then you can verify the replace using:

go list -m -f '{{.Path}} => {{.Replace}}' all | grep jwt
github.com/dgrijalva/jwt-go => github.com/golang-jwt/jwt v3.2.1+incompatible

@asaha123
Copy link
Author

asaha123 commented Aug 2, 2021

I will leave a pointer to the indirect dependency issues:

Once the above are resolved, we can remove the replace directives.

@eli-darkly
Copy link
Contributor

@asaha-atlassian:

FWIW, for folks using the ld-relay library, we will still need to add the replace directive

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants